vtbag
diff --git a/‎src/content/docs/tips/view-transition-fails-and-fixes.mdx‎
Lines changed: 2 additions & 2 deletions b/‎src/content/docs/tips/view-transition-fails-and-fixes.mdx‎
Lines changed: 2 additions & 2 deletions
@@ -40,15 +40,15 @@ or [opening an issue on GitHub!](https://github.com/vtbag/website/issues/new?tem
   Uncaught (in promise) AbortError: Transition was skipped
   ``` 
 
-  It might seem best to place this rule together with your global view transition styles in a shared stylesheet and [include it on every page](/fwvt/enabling/#including-css-on-all-pages). This is fine if the opt-in to view transitions is at the start of the stylesheet.
+  It might seem best to place this rule together with your global view transition styles in a shared stylesheet and [include it on every page](/fwvt/enabling/#including-css-on-all-pages). This seems to be fine if the @view-transition opt-in is at the start of the stylesheet. But I recommend to place it in an style element in the `<head>`, see next section. 
 
 #### Potential Pitfall: Unreliable Detection of the Opt-in
 
   A particular pitfall occurs when the `@view-transition` at-rule is present but not reliably detected by the browser. This can happen in Chrome, for example, when the at-rule is placed in an external stylesheet after tons of other CSS.
 
   According to the specification, the check for `@view-transition { navigation: auto }` happens together with the `pagereveal` event just before the first rendering. In theory, that means the browser should wait for render blocking resources such as external stylesheets linked in the `<head>`. However, Chrome may perform this check [without necessarily waiting for external CSS](https://issues.chromium.org/issues/383014860#comment9).
 
-  The safest approach is therefore to place the opt in for cross document view transitions early in the `<head>` inside an inline `<style>` element.
+  The safest approach is therefore to place the opt-in for cross-document view transitions inside a `<style>` elementearly within the `<head>`.