minor nits

Author: cephalin

articles/app-service/configure-sidecar.md

@@ -75,7 +75,7 @@ Add the `Microsoft.Web/sites/sitecontainers` resource type to an app. To pull a
 
 For more information, see [Microsoft.Web sites/sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers).
 
-## How to Define Environment Variables for a Sidecar
+## Set environment variables
 
 In a Linux app, all containers (main and sidecars) share environment variables. To override a specific variable for a sidecar, add it in the sidecar's configuration.
 
@@ -128,7 +128,7 @@ From the Azure portal, you can add a Datadog sidecar extension to collect logs,
 
 Before you add the Datadog sidecar extension, add the Datadog tracer setup in your Dockerfile, similar to the script example for code-based apps.
 
-## Add the Phi-3/Phi-4
+## Add the Phi-3/Phi-4 sidecar extension
 
 From the Azure portal, you can add a Phi-3 or Phi-4 sidecar extension to your app to provide a local inference model for AI workloads. Your app must be in a pricing tier that supports the inferencing needs. For unsupported tiers, you don't see the options for the Phi-3/Phi-4 sidecar extensions.
 
@@ -173,4 +173,10 @@ Example configuration:
 - Container4 does not share a volume with the others.
 
 > [!Note]
-> For code-based Linux apps, the built-in Linux container cannot use volume mounts.
+> For code-based Linux apps, the built-in Linux container cannot use volume mounts.
+
+## More resources
+
+- [Sidecars overview](overview-sidecar.md)
+- [Migrate Docker Compose apps to sidecars in Azure App Service](migrate-sidecar-multi-container-apps.md)
+- [Microsoft Q&A for Azure App Service](/answers/tags/436/azure-app-service)

articles/app-service/migrate-sidecar-multi-container-apps.md

@@ -14,14 +14,13 @@ If you're running a Docker Compose app in Azure App Service, you should migrate
 - Script-based migration - recommended for simple setups.
 - Manual migration
 
-## a. Prerequisites
+## Prerequisites
 
 - PowerShell
 - Azure CLI
 - Docker (for building and pushing images)
-- Text editor (e.g., VS Code)
 
-## Script-based migration
+## Migrate with a script
 
 If your Docker Compose file is straightforward, you can use the official migration script to automate the process.
 
@@ -42,9 +41,9 @@ If your Docker Compose file is straightforward, you can use the official migrati
       -targetPort "<targetPort>"
     ```
 
-If your registry requires authentication, the script prompts you to provide `dockerRegistryServerUsername` and `dockerRegistryServerPassword` interactively.
+    If your registry requires authentication, the script prompts you to provide `dockerRegistryServerUsername` and `dockerRegistryServerPassword` interactively.
 
-## Manual migration
+## Migrate manually
 
 1. Sign in to Azure and set your subscription.
 
@@ -116,26 +115,26 @@ If your registry requires authentication, the script prompts you to provide `doc
     az webapp deployment slot swap --name <webapp-name> --resource-group <resource-group> --slot <slot-name> --target-slot production
     ```
 
-## Mapping of Docker Compose Attributes and Sidecar Configuration
+## Mapping of Docker Compose attributes and sidecar configuration
 
 The following Docker Compose fields are mapped to sidecar configuration:
 
-| Docker Compose | Sidecar Configuration | Notes |
+| Docker Compose | Sidecar configuration | Notes |
 |---------------|----------------------|-------|
 | `command`, `entrypoint` | `startUpCommand` | |
 | `environment` | `environmentVariables` | |
 | `image` | `image` | |
-| `ports` | `targetPort` | Only ports 80 and 8080 are supported for external traffic |
-| `volumes` | `volumeMounts` | Persistent Azure storage not supported |
+| `ports` | `targetPort` | Only ports 80 and 8080 are supported for external traffic. |
+| `volumes` | `volumeMounts` | Persistent Azure storage not supported. |
 
 The following Docker Compose fields are unsupported in sidecars:
 
 | Docker Compose Field | Support | Notes |
 |---------------------|---------|-------|
-| `build` | Not allowed | Pre-build and push images to a registry |
-| `depends_on` | Ignored | No container startup ordering guaranteed |
-| `networks` | Ignored | Network handled internally |
-| `secrets` | Ignored | Use App Settings or Key Vault |
+| `build` | Not allowed | Pre-build and push images to a registry. |
+| `depends_on` | Ignored | No container startup ordering is guaranteed. |
+| `networks` | Ignored | Networking is handled internally. |
+| `secrets` | Ignored | Use App Service app settings or Key Vault for secrets. |
 | `volumes` using `{WEBAPP_STORAGE_HOME}` or `{WEBSITES_ENABLE_APP_SERVICE_STORAGE}` | Not supported | |
 
 ## Migration limitations and considerations

articles/app-service/overview-sidecar.md

@@ -11,9 +11,9 @@ author: cephalin
 
 In Linux App Service apps (built-in containers and custom containers), a sidecar is an auxiliary container that runs in the same environment as your main app container. Sidecars can provide supporting services (like telemetry, caching, or AI inference) and are managed as part of your App Service app.
 
-## Why use Sidecars on App Service?
+## Why use sidecars on App Service?
 
-Sidecars enable you to add new capabilities—such as monitoring, caching, AI, or custom logic—without modifying your main application code (in built-in containers) or your main container (in custom containers). Benefits include:
+Sidecars enable you to add new capabilities, such as monitoring, caching, AI, or custom logic, without modifying your main application code (in built-in containers) or your main container (in custom containers). Benefits include:
 
 - **Separation of concerns:** Add or update services independently of your main app.
 - **Extensibility:** Integrate prebuilt or custom extensions (e.g., OpenTelemetry, Redis, Datadog, Phi-3/4 AI models).