Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides command examples for Windows (PowerShell and Cmd) alongside bash, but Windows-specific instructions and tools (PowerShell, Cmd) are often listed before or more prominently than Linux/macOS equivalents. The use of Windows command shells is explicit in several sections, and Windows-centric patterns (such as 'py' for Python, which is a Windows launcher) are used in examples. Linux instructions are present but sometimes appear after Windows ones or are less detailed.
Recommendations
- Ensure Linux/macOS instructions are presented before or alongside Windows instructions, not after.
- Provide parity in command examples, ensuring bash/Linux/macOS commands are as detailed and prominent as Windows/PowerShell/Cmd examples.
- Avoid using Windows-specific tools or patterns (such as 'py' launcher) in cross-platform sections; prefer 'python3' for Python commands.
- Where possible, group instructions by OS (Linux/macOS, Windows) and clarify which commands apply to which environment.
- Review all code blocks and tabs to ensure Linux/macOS users have clear, first-class guidance.
- Explicitly mention cross-platform compatibility for all tools (e.g., Azure Developer CLI, Azurite, Azure Functions Core Tools) and provide installation instructions for Linux/macOS where relevant.
Create Pull Request