chore: Move Examples section after Values

src/content/docs/reference/policies/3rdparty.mdx

@@ -8,16 +8,16 @@ Allow WebExtensions to configure policies.
 For more information, see [Adding policy support to your extension](https://extensionworkshop.com/documentation/enterprise/enterprise-development/#how-to-add-policy).
 For GPO and Intune, the extension developer should provide an ADMX file.
 
-## Examples
-
-<PolicyExample policy="3rdparty" />
-
 ## Values
 
 - `Extensions`: An object keyed by extension ID.
   The value for each ID is the configuration passed to that extension.
   Firefox does not define those keys and values, the extension does, so check the extension's documentation for what it accepts.
 
+## Examples
+
+<PolicyExample policy="3rdparty" />
+
 ## macOS
 
 ```xml

src/content/docs/reference/policies/AIChatbot.mdx

@@ -7,10 +7,6 @@ category: "Content settings"
 Configure the AI chatbot sidebar, including which built-in providers are available and the ability to add custom providers.
 For more information, see [Access AI chatbots in Firefox](https://support.mozilla.org/en-US/kb/ai-chatbot) on support.mozilla.org.
 
-## Examples
-
-<PolicyExample policy="AIChatbot" />
-
 ## Values
 
 - `Providers`: Configures the available AI chatbot providers.
@@ -42,6 +38,10 @@ For more information, see [Access AI chatbots in Firefox](https://support.mozill
     - `Quiz`
     - `Proofread`
 
+## Examples
+
+<PolicyExample policy="AIChatbot" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AIControls.mdx

@@ -7,10 +7,6 @@ category: "Miscellaneous"
 Configure AI controls.
 For more information, see [Block generative AI features with Firefox AI controls](https://support.mozilla.org/en-US/kb/firefox-ai-controls) on support.mozilla.org.
 
-## Examples
-
-<PolicyExample policy="AIControls" />
-
 ## Values
 
 Each key controls the availability of a specific AI feature.
@@ -33,6 +29,10 @@ All keys accept the following sub-keys:
     For on-device AI, any models already downloaded are removed.
 - `Locked`: if `true`, the user cannot change the setting.
 
+## Examples
+
+<PolicyExample policy="AIControls" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AccessConnector.mdx

@@ -8,10 +8,6 @@ Configure an Access Connector for proxying web traffic.
 When this policy is set, Firefox routes traffic through the server given by `Host` and `Port`.
 If `MatchPatterns` is set, only URLs matching those patterns are routed through the connector.
 
-## Examples
-
-<PolicyExample policy="AccessConnector" />
-
 ## Values
 
 - `Host`: A string that defines the hostname or IP address of the proxy server to use.
@@ -23,6 +19,10 @@ If `MatchPatterns` is set, only URLs matching those patterns are routed through
   Unlike most policies, this defaults to `true`.
   Set it to `false` to apply the settings as defaults that users can still change.
 
+## Examples
+
+<PolicyExample policy="AccessConnector" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AllowFileSelectionDialogs.mdx

@@ -6,15 +6,15 @@ category: "Browser UI"
 
 Enable or disable file selection dialogs.
 
-## Examples
-
-<PolicyExample policy="AllowFileSelectionDialogs" />
-
 ## Values
 
 - Set to `true` to allow file selection dialogs. This is the same as omitting the policy.
 - Set to `false` to stop Firefox opening file selection dialogs. Downloads go straight to the download directory and the user cannot change that.
 
+## Examples
+
+<PolicyExample policy="AllowFileSelectionDialogs" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AllowedDomainsForApps.mdx

@@ -8,17 +8,17 @@ Define domains allowed to access Google Workspace.
 This policy is based on the [Chrome policy](https://chromeenterprise.google/policies/#AllowedDomainsForApps) of the same name.
 If this policy is enabled, users can only access Google Workspace using accounts from the specified domains. If you want to allow Gmail, you can add `consumer_accounts` to the list.
 
-## Examples
-
-<PolicyExample policy="AllowedDomainsForApps" />
-
 ## Values
 
 `AllowedDomainsForApps` expects a comma-separated list of domains, sent to Google as the `X-GoogApps-Allowed-Domains` header:
 
 - A domain, such as `example.com`, allows Google Workspace accounts from that domain.
 - `consumer_accounts`: a keyword that allows personal Gmail accounts alongside whichever Workspace domains you list. See the [Chrome equivalent](https://chromeenterprise.google/policies/allowed-domains-for-apps/) for more details.
 
+## Examples
+
+<PolicyExample policy="AllowedDomainsForApps" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AppAutoUpdate.mdx

@@ -11,15 +11,15 @@ When the policy is disabled, application updates are downloaded and the user can
 
 If you have disabled updates via [`DisableAppUpdate`](/reference/policies/disableappupdate/), this policy has no effect.
 
-## Examples
-
-<PolicyExample policy="AppAutoUpdate" />
-
 ## Values
 
 - Set to `true` to install application updates without user approval, and prevent the user from turning automatic updates off. The operating system might still require approval.
 - Set to `false` to download updates but let the user choose when to install them, and prevent the user from turning automatic updates on.
 
+## Examples
+
+<PolicyExample policy="AppAutoUpdate" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AppUpdatePin.mdx

@@ -18,17 +18,17 @@ You can specify a major and minor version as `xx.xx.` (e.g, `140.0.`) and Firefo
 You should specify a version that exists or is guaranteed to exist.
 If you specify a version that doesn't exist, Firefox will update beyond that version.
 
-## Examples
-
-<PolicyExample policy="AppUpdatePin" />
-
 ## Values
 
 `AppUpdatePin` expects a version prefix ending in a dot:
 
 - `MAJOR.`, such as `140.`, pins Firefox to the major version and allows every update within it.
 - `MAJOR.MINOR.`, such as `140.0.`, pins Firefox to the minor version and allows only patch updates within it.
 
+## Examples
+
+<PolicyExample policy="AppUpdatePin" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AppUpdateURL.mdx

@@ -6,14 +6,14 @@ category: "Device update settings"
 
 Change the URL for application update if you are providing Firefox updates from a custom update server.
 
-## Examples
-
-<PolicyExample policy="AppUpdateURL" />
-
 ## Values
 
 `AppUpdateURL` expects the URL of the update XML on your update server, such as `https://www.example.com/update.xml`.
 
+## Examples
+
+<PolicyExample policy="AppUpdateURL" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/Authentication.mdx

@@ -7,10 +7,6 @@ category: "Authentication"
 Configure sites that support integrated authentication.
 See [Integrated authentication](https://htmlpreview.github.io/?https://github.com/mdn/archived-content/blob/main/files/en-us/mozilla/integrated_authentication/raw.html) for more information.
 
-## Examples
-
-<PolicyExample policy="Authentication" />
-
 ## Values
 
 - `SPNEGO`: A list of sites permitted to use SPNEGO (Kerberos) authentication.
@@ -25,6 +21,10 @@ See [Integrated authentication](https://htmlpreview.github.io/?https://github.co
   Unlike most policies, this defaults to `true`.
   Set it to `false` to apply the values as defaults that users can still change.
 
+## Examples
+
+<PolicyExample policy="Authentication" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AutoLaunchProtocolsFromOrigins.mdx

@@ -10,10 +10,6 @@ The origin is the scheme (protocol), hostname (domain), and port of the URL used
 The syntax of this policy is the same as the [Chrome AutoLaunchProtocolsFromOrigins policy](https://chromeenterprise.google/policies/#AutoLaunchProtocolsFromOrigins) except that you can only use valid origins (not just hostnames).
 This also means that you cannot specify a wildcard (`*`) for all origins.
 
-## Examples
-
-<PolicyExample policy="AutoLaunchProtocolsFromOrigins" />
-
 ## Values
 
 Each entry in the list accepts the following keys:
@@ -23,6 +19,10 @@ Each entry in the list accepts the following keys:
   Each origin is a scheme, hostname and optional port.
   Paths and wildcards are not supported.
 
+## Examples
+
+<PolicyExample policy="AutoLaunchProtocolsFromOrigins" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AutofillAddressEnabled.mdx

@@ -9,15 +9,15 @@ Enables or disables autofill for addresses.
 This only applies when address autofill is enabled for a particular Firefox version or region.
 See [Automatically fill in your address on web forms](https://support.mozilla.org/kb/automatically-fill-your-address-web-forms) for more information.
 
-## Examples
-
-<PolicyExample policy="AutofillAddressEnabled" />
-
 ## Values
 
 - Set to `true` to save and autofill addresses, and prevent the user from changing it.
 - Set to `false` to stop saving and autofilling addresses, and prevent the user from changing it.
 
+## Examples
+
+<PolicyExample policy="AutofillAddressEnabled" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/AutofillCreditCardEnabled.mdx

@@ -8,15 +8,15 @@ Enables or disables autofill for payment methods.
 
 This only applies when payment method autofill is enabled for a particular Firefox version or region. See [Automatically fill in credit card data](https://support.mozilla.org/kb/credit-card-autofill) for more information.
 
-## Examples
-
-<PolicyExample policy="AutofillCreditCardEnabled" />
-
 ## Values
 
 - Set to `true` to save and autofill payment methods, and prevent the user from changing it.
 - Set to `false` to stop saving and autofilling payment methods, and prevent the user from changing it.
 
+## Examples
+
+<PolicyExample policy="AutofillCreditCardEnabled" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/BackgroundAppUpdate.mdx

@@ -15,15 +15,15 @@ If you are having trouble getting the background task to run, verify your config
 > [!NOTE]
 > The `BackgroundAppUpdate` policy has no effect if you have disabled updates via the [`DisableAppUpdate`](/reference/policies/disableappupdate/) policy or disabled automatic updates via the [`AppAutoUpdate`](/reference/policies/appautoupdate/) policy.
 
-## Examples
-
-<PolicyExample policy="BackgroundAppUpdate" />
-
 ## Values
 
 - Set to `true` to install updates in the background, and prevent the user from turning background updates off.
 - Set to `false` to stop updates being installed in the background, and prevent the user from turning them on.
 
+## Examples
+
+<PolicyExample policy="BackgroundAppUpdate" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/BlockAboutAddons.mdx

@@ -6,15 +6,15 @@ category: "Extensions"
 
 Block access to the Add-ons Manager (`about:addons`).
 
-## Examples
-
-<PolicyExample policy="BlockAboutAddons" />
-
 ## Values
 
 - Set to `true` to block access to the Add-ons Manager (`about:addons`).
 - Set to `false` to leave the Add-ons Manager available. This is the same as not setting the policy.
 
+## Examples
+
+<PolicyExample policy="BlockAboutAddons" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/BlockAboutConfig.mdx

@@ -6,15 +6,15 @@ category: "Security"
 
 Block access to Advanced Preferences (`about:config`).
 
-## Examples
-
-<PolicyExample policy="BlockAboutConfig" />
-
 ## Values
 
 - Set to `true` to block access to `about:config`. This also turns off browser chrome debugging (`devtools.chrome.enabled`).
 - Set to `false` to leave `about:config` available. This is the same as not setting the policy.
 
+## Examples
+
+<PolicyExample policy="BlockAboutConfig" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/BlockAboutProfiles.mdx

@@ -6,15 +6,15 @@ category: "Security"
 
 Block access to About Profiles (`about:profiles`).
 
-## Examples
-
-<PolicyExample policy="BlockAboutProfiles" />
-
 ## Values
 
 - Set to `true` to block the profile pages: `about:profiles`, `about:profilemanager`, `about:editprofile`, `about:newprofile` and `about:deleteprofile`.
 - Set to `false` to leave the profile pages available. This is the same as not setting the policy.
 
+## Examples
+
+<PolicyExample policy="BlockAboutProfiles" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/BlockAboutSupport.mdx

@@ -6,15 +6,15 @@ category: "Security"
 
 Block access to Troubleshooting Information (`about:support`).
 
-## Examples
-
-<PolicyExample policy="BlockAboutSupport" />
-
 ## Values
 
 - Set to `true` to block access to troubleshooting information (`about:support`).
 - Set to `false` to leave `about:support` available. This is the same as not setting the policy.
 
+## Examples
+
+<PolicyExample policy="BlockAboutSupport" />
+
 ## Windows (GPO)
 
 ```

src/content/docs/reference/policies/Bookmarks.mdx

@@ -12,10 +12,6 @@ Add bookmarks in either the bookmarks toolbar or menu.
 
 If you want to clear all bookmarks set with this policy, you can set the value to an empty array (`[]`). This can be on Windows via the new Bookmarks (JSON) policy available with GPO and Intune.
 
-## Examples
-
-<PolicyExample policy="Bookmarks" />
-
 ## Values
 
 Each entry in the list accepts the following keys:
@@ -28,6 +24,10 @@ Each entry in the list accepts the following keys:
 - `Folder`: The name of a folder to put the bookmark in.
   The folder is created if it doesn't exist, and bookmarks that name the same folder are grouped together.
 
+## Examples
+
+<PolicyExample policy="Bookmarks" />
+
 ## Windows (GPO)
 
 ```