About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
windows_file_naming
Summary:
The documentation generally maintains good cross-platform parity, but there is a subtle Windows bias in the order and phrasing of some instructions. Windows-specific file naming conventions (e.g., 'handler.exe') are mentioned first or as the default, and Windows-specific commands (e.g., 'set' in cmd) are given in a dedicated section, while Linux/macOS equivalents are grouped together. In configuration steps, Windows is often referenced explicitly or first, and Linux is sometimes presented as an alternative rather than the default, despite the deployment target being Linux.
Recommendations:
- When referencing executable names, mention the Linux version ('handler') first, with Windows ('handler.exe') as a note or alternative.
- In configuration instructions, avoid phrasing like 'on Windows, set it to handler.exe'—instead, use 'set to handler (or handler.exe on Windows)'.
- Present Linux/macOS instructions before Windows, especially since the deployment target is Linux.
- Where possible, use cross-platform command syntax or provide all platform variants together, not with Windows as a separate afterthought.
- Explicitly state that the primary deployment and runtime environment is Linux, and clarify that Windows-specific steps are only needed for local development on Windows.
- Ensure that screenshots and terminal outputs are balanced between platforms or are platform-neutral.
Create pull request