Move key changes

Author: inancgumus

src/data/markdown/translated-guides/en/03 Using k6 browser/04 Migrating to k6 v0-46.md

@@ -19,18 +19,6 @@ Users no longer need to use the `K6_BROWSER_ENABLED` flag when running browser t
 </Blockquote>
 
 
-## Key changes in the new API
-
-The updated version introduces notable structural changes in its operation and API. Let's take a look at them.
-
-* [Scenario options](#scenario-options) must now be defined for running browser tests.
-* The [import path](#import-path) for the browser module has switched from `chromium` to [browser](/javascript-api/k6-experimental/browser/#browser-module-api).
-* Browser options can now only be set using certain [environment variables](/javascript-api/k6-experimental/browser/#browser-module-options). The `launch()` method, used earlier for this purpose, has been removed.
-* [Simplified resource management](#simplified-resource-management). The browser now starts automatically, managed by the browser module itself. There's no need to use `browser.close()` anymore.
-* [Single browser context per iteration](#browser-context-limit). Users can now only run a single [BrowserContext](/javascript-api/k6-experimental/browser/browsercontext/) at a time in the same iteration.
-
-
-
 ## Before and after comparison
 
 Let's start with an overview of the primary differences between the previous and new versions of the k6 browser API. Subsequent sections will delve into each difference in detail.
@@ -92,6 +80,16 @@ export default async function () {
 </CodeGroup>
 
 
+## Key changes in the new API
+
+The updated version introduces notable structural changes in its operation and API. Let's take a look at them.
+
+* [Scenario options](#scenario-options) must now be defined for running browser tests.
+* The [import path](#import-path) for the browser module has switched from `chromium` to [browser](/javascript-api/k6-experimental/browser/#browser-module-api).
+* Browser options can now only be set using certain [environment variables](/javascript-api/k6-experimental/browser/#browser-module-options). The `launch()` method, used earlier for this purpose, has been removed.
+* [Simplified resource management](#simplified-resource-management). The browser now starts automatically, managed by the browser module itself. There's no need to use `browser.close()` anymore.
+* [Single browser context per iteration](#browser-context-limit). Users can now only run a single [BrowserContext](/javascript-api/k6-experimental/browser/browsercontext/) at a time in the same iteration.
+