Azure Maps

The documentation page includes a code sample for installing npm packages using PowerShell syntax (`npm install --save-dev style-loader css-loader`), which is specific to Windows. No equivalent Linux/macOS shell example is provided. Additionally, the only explicit shell example is Windows-oriented, and it appears before any mention of cross-platform usage.

• Provide Linux/macOS shell equivalents (e.g., Bash) alongside PowerShell commands.
• Use generic shell commands (`npm install ...`) without platform-specific prefixes unless necessary.
• Add a note clarifying that the npm install command works on all platforms, or show both Windows and Linux/macOS examples side by side.
• Review other tooling references to ensure parity (e.g., mention that webpack and npm are cross-platform).

The documentation page demonstrates a mild Windows bias by using PowerShell syntax for npm install commands and listing Windows-centric tooling (PowerShell) before any mention of Linux/macOS equivalents. No Linux/macOS-specific instructions or shell examples are provided, and the only CLI example uses PowerShell syntax.

• Provide npm install commands using generic shell syntax (e.g., $ npm install ...), which works across Windows, Linux, and macOS.
• Explicitly mention that the npm commands can be run in any terminal (e.g., Command Prompt, PowerShell, Bash, zsh, etc.).
• Add notes or examples for Linux/macOS users, especially for steps involving local development and bundling.
• Avoid using PowerShell-specific syntax unless necessary, or provide both PowerShell and Bash/zsh examples.

The documentation primarily demonstrates deployment via the Azure Portal (web UI), which is cross-platform, but references to alternative deployment methods (Azure PowerShell, Azure CLI, REST API) are brief and lack examples. The only command-line examples provided use Azure CLI, which is cross-platform, but there are no PowerShell-specific examples. However, the link for 'Deploy templates' points to a PowerShell-focused page, suggesting a Windows-first orientation. There are no explicit Linux/macOS instructions or screenshots, and no mention of platform-specific considerations.

• Provide explicit examples for both Azure CLI and Azure PowerShell, and clarify their cross-platform availability.
• Include Linux/macOS-specific instructions or screenshots where relevant.
• Ensure links to deployment methods include both CLI and PowerShell documentation, not just PowerShell.
• Mention that Azure CLI works on Windows, Linux, and macOS, and provide installation guidance for each.

The documentation consistently uses PowerShell syntax (e.g., 'npm install' and 'npm init' shown as PowerShell code blocks) for all command-line examples, which may imply a Windows-centric approach. There is no mention of Linux/macOS terminals or shell environments, and no alternative shell syntax is provided. While the actual commands are cross-platform, the presentation may cause confusion or friction for non-Windows users.

• Use generic shell code blocks (e.g., 'bash' or no language tag) for npm commands, since they are identical across platforms.
• Add a note clarifying that the commands work on Linux/macOS and Windows, and that users should run them in their preferred terminal.
• Consider showing both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) command examples if platform-specific differences exist.
• Avoid using 'powershell' as the code block language unless PowerShell-specific syntax is required.