Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, maintaining parity in command-line instructions. However, in the 'Send requests' section, the PowerShell example is significantly more complex and Windows-specific, while the Bash example uses standard Linux utilities. The PowerShell example is presented with equal prominence, but the explanations and referenced tools (e.g., PowerShell runspaces) are Windows-centric and may not be familiar to Linux users. Additionally, the instructions for opening a shell refer to 'bash shell' for Bash and 'command prompt and enter PowerShell' for PowerShell, subtly prioritizing Windows terminology. There is no explicit mention of Linux alternatives for the PowerShell-specific patterns, nor is there guidance for macOS users.
Recommendations
- Add explicit instructions for macOS users, clarifying that Bash commands work on macOS and most Linux distributions.
- In the 'Send requests' section, provide a brief explanation that Bash commands are native to Linux/macOS, while PowerShell commands are for Windows users.
- Consider mentioning cross-platform shells such as PowerShell Core, which runs on Linux and macOS, and clarify any differences in command syntax or behavior.
- Where PowerShell examples use advanced Windows-specific constructs (e.g., runspaces), offer alternative Bash or Linux-native approaches for concurrency, or reference tools like GNU Parallel.
- Review terminology to avoid subtle Windows bias (e.g., use 'terminal' or 'shell' instead of 'command prompt' when referring to opening a shell).
Create Pull Request