Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity in basic usage. However, in the 'Send requests' section, the PowerShell example is significantly more complex than the Bash equivalent, relying on advanced Windows/PowerShell constructs (runspaces, Invoke-WebRequest) that have no direct Linux/Bash counterpart. Additionally, instructions for opening a new shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for Windows, subtly prioritizing Windows terminology. The Bash examples use standard Linux utilities (seq, xargs, curl), but the PowerShell example is much longer and more involved, which may suggest a bias toward Windows users by providing more detailed guidance for PowerShell. No Linux-specific tools or patterns are mentioned first or exclusively, but the PowerShell examples are always present and sometimes more elaborate.
Recommendations
- Ensure that Bash and PowerShell examples are equally detailed and provide similar levels of explanation.
- Consider adding a brief explanation for how to run the Bash commands on Windows (e.g., via WSL or Git Bash), to help Windows users who prefer Bash.
- For the 'Send requests' section, provide a simpler PowerShell example if possible, or explain why the PowerShell approach is more complex.
- Avoid phrasing that assumes Windows as the default (e.g., 'Open a new command prompt'), and use more neutral language such as 'Open a new shell'.
- If possible, add troubleshooting notes for both Bash and PowerShell environments, not just one.
Create Pull Request