diff --git a/src/content/docs/en/guides/upgrade-to/v5.mdx b/src/content/docs/en/guides/upgrade-to/v5.mdx
index f4d36c90aa3df..08d75ab2ee316 100644
--- a/src/content/docs/en/guides/upgrade-to/v5.mdx
+++ b/src/content/docs/en/guides/upgrade-to/v5.mdx
@@ -531,14 +531,14 @@ In the event of route collisions, where two routes of equal route priority attem
 
 <SourcePR number="11791" title="Make directRenderScript the default"/>
 
-In Astro v4.x, `experimental.directRenderScript` was an optional flag to directly render `<scripts>` as declared in `.astro` files (including existing features like TypeScript, importing `node_modules`, and deduplicating scripts). This strategy prevented scripts from being executed in places where they were not used.
+In Astro v4.x, `experimental.directRenderScript` was an optional flag to directly render `<scripts>` as declared in `.astro` files (including existing features like TypeScript, importing `node_modules`, and deduplicating scripts). This strategy prevented scripts from being executed in places where they were not used. Additionally, conditionally rendered scripts were previously implicitly inlined, as if an `is:inline` directive was automatically added to them.
 
-Astro 5.0 removes this experimental flag and makes this the new default behavior in Astro: scripts are no longer hoisted to the `<head>`, multiple scripts on a page are no longer bundled together, and a `<script>` tag may interfere with CSS styling.
-
-Additionally, conditionally rendered scripts were previously implicitly inlined, as if an `is:inline` directive was automatically added to them. In Astro 5, this behavior is no longer implicit.
+Astro 5.0 removes this experimental flag and makes this the new default behavior in Astro: scripts are no longer hoisted to the `<head>`, multiple scripts on a page are no longer bundled together, and a `<script>` tag may interfere with CSS styling. Additionally, conditionally rendered scripts are no longer implicitly inlined.
 
 #### What should I do?
 
+Please review your `<script>` tags and ensure they behave as desired.
+
 If you previously had conditionally rendered `<script>` tags, you will need to add an `is:inline` attribute to preserve the same behavior as before:
 
 ```astro title="src/components/MyComponent.astro" ins="is:inline"
@@ -554,8 +554,6 @@ const { showAlert } = Astro.props;
 }
 ```
 
-Please review your `<script>` tags and ensure they behave as desired.
-
 <ReadMore>Read more about [using `script` tags in Astro](/en/guides/client-side-scripts/#using-script-in-astro).</ReadMore>
 
 ## Breaking Changes
