docs: minor updates

content/docs/introduction/branch-restore.md

@@ -227,14 +227,17 @@ curl --request POST \
 In this example, we are restoring a development branch `dev/alex` (branch ID `br-twilight-river-31791249`) to the latest data (head) of its parent branch `br-jolly-star-07007859`. Note that we don't include any time identifier or backup branch name; this is a straight reset of the branch to the head of its parent.
 
 ```bash shouldWrap
-curl --request POST \ // [!code word:br-twilight-river-31791249]
+curl --request POST \
+     # [!code word:br-twilight-river-31791249]
      --url https://console.neon.tech/api/v2/projects/floral-disk-86322740/branches/br-twilight-river-31791249/restore \
      --header 'Accept: application/json' \
      --header "Authorization: Bearer $NEON_API_KEY" \
-     --header 'Content-Type: application/json' \ // [!code word:br-jolly-star-07007859]
+     --header 'Content-Type: application/json' \
      --data '
 {
-  "source_branch_id": "br-jolly-star-07007859"}
+  # [!code word:br-jolly-star-07007859]
+  "source_branch_id": "br-jolly-star-07007859"
+}
 ' | jq
 ```
 
@@ -243,13 +246,15 @@ curl --request POST \ // [!code word:br-twilight-river-31791249]
 In this example, we are restoring branch `dev/jordan` (branch ID `br-damp-smoke-91135977`) to branch `dev/alex` (branch ID `br-twilight-river-31791249`) at the point in time of `Feb 26, 2024 12:00:00.000 AM`.
 
 ```bash shouldWrap
-curl --request POST \ // [!code word:br-damp-smoke-91135977]
+curl --request POST \
+     # [!code word:br-damp-smoke-91135977]
      --url https://console.neon.tech/api/v2/projects/floral-disk-86322740/branches/br-damp-smoke-91135977/restore \
      --header 'Accept: application/json' \
-     --header "Authorization: Bearer $NEON_API_KEY" \ //  [!code word:br-jolly-star-07007859]
+     --header "Authorization: Bearer $NEON_API_KEY" \
      --header 'Content-Type: application/json' \
      --data '
 {
+  # [!code word:br-jolly-star-07007859]
   "source_branch_id": "br-jolly-star-07007859",
   "source_timestamp": "2024-02-26T12:00:00Z"
 }

content/docs/introduction/regions.md

@@ -26,10 +26,6 @@ Neon offers project deployment in multiple AWS and Azure regions. To minimize la
 - 🇺🇸 Azure West US 3 region (Arizona) — `azure-westus3`
 - 🇩🇪 Azure Germany West Central region (Frankfurt) — `azure-gwc`
 
-<Admonition type="note" title="Deployment options on azure">
-For information about Neon deployment options on Azure, see [Neon on Azure](/docs/manage/azure).
-</Admonition>
-
 ## Request a region
 
 <RequestForm type="region" />

content/docs/manage/branches.md

@@ -38,10 +38,9 @@ To create a branch:
 3. Click **New branch** to open the branch creation dialog.
 4. Specify a branch name.
 5. Select a **branch setup** option. If you're interested in schema-only branches, see [Schema-only branches](/docs/guides/branching-schema-only).
-
-<Admonition type="note">
-When creating a branch with past data, you can only specify a date and time that falls within your [restore window](/docs/manage/projects#configure-restore-window).
-</Admonition>
+   <Admonition type="note">
+   When creating a branch with past data, you can only specify a date and time that falls within your [restore window](/docs/manage/projects#configure-restore-window).
+   </Admonition>
 
 6. By default, **Automatically delete branch after** is checked with 1 day selected to help prevent unused branches from accumulating. You can choose 1 hour, 1 day, or 7 days, or uncheck to disable. This is useful for CI/CD pipelines and short-lived development environments. Note: This default only applies when creating branches through the Console; API and CLI branches have no expiration by default. Refer to our [Branch expiration guide](/docs/guides/branch-expiration) for details.
 7. Click **Create new branch**.