Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 2026-2050 of 2334 flagged pages
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. PowerShell is mentioned as a primary automation tool, and some links and examples reference Windows-specific tabs or features before Linux equivalents. Linux tools and examples are present but often secondary or implied rather than explicit. No critical sections are Windows-only, but Linux/macOS users may experience minor friction.
Recommendations
- When listing automation tools, mention Bash/CLI and Linux SDKs equally alongside PowerShell.
- Ensure linked guides and quickstarts include both Windows and Linux instructions/examples, not just Windows tabs.
- Where runbooks or automation are discussed, provide explicit Linux examples (e.g., Bash scripts, Linux runbook tabs) in addition to PowerShell.
- Review linked pages (e.g., 'connect VMware vCenter to Azure Arc using the helper script') to ensure Linux parity in instructions.
- When referencing Azure portal tabs or guides, avoid defaulting to Windows unless the feature is Windows-only.
Create Pull Request
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or exclusive Windows tools mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are suitable for Linux/macOS users.
- Ensure screenshots and portal instructions are platform-neutral or clarify any OS-specific nuances if relevant.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux/macOS parity. However, PowerShell examples are sometimes shown immediately after Bash, and some minor details (like base64 encoding) are explained separately for Windows and Linux. There is no evidence of Windows-only tools or missing Linux examples, but the structure sometimes places Windows/PowerShell examples before or equally with Bash, which may create minor friction for Linux users.
Recommendations
- Ensure Bash examples are always shown first in each code tab, as Bash is the default shell for most Linux/macOS users.
- Where possible, clarify any OS-specific steps (such as file encoding or base64 commands) in a single, unified note rather than splitting by shell.
- Review PowerShell-specific explanations to ensure they are not prioritized over Bash/Linux explanations.
- Consider adding explicit notes about cross-platform compatibility, especially for commands that may behave differently on Windows vs. Linux.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all commands, but consistently lists Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. The only detectable bias is the minor ordering of Bash examples before PowerShell.
Recommendations
- Continue providing both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Optionally alternate the order of examples or explicitly state that both platforms are supported equally.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. There is no evidence of missing Linux examples or exclusive use of Windows tools; all commands use the cross-platform Azure CLI. However, the presence of PowerShell examples and the explicit PowerShell tab may indicate a mild Windows bias, especially since PowerShell is less common on Linux/macOS environments compared to Bash.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS users.
- Clarify in the introduction that all commands use Azure CLI, which is cross-platform.
- Optionally, add a note that PowerShell examples are provided for users who prefer PowerShell, but Bash is recommended for Linux/macOS.
- Ensure that any references to file paths, environment variables, or scripting conventions are valid for both Linux and Windows shells.
- If possible, provide a short section or FAQ for macOS users to highlight any platform-specific considerations.
Azure Arc
Create a Basic Solution with Common Configurations with Workload Orchestration
...ation/quickstart-solution-with-common-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently shown before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All commands use the Azure CLI, which is cross-platform.
Recommendations
- Continue to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs, or clarify that Bash is shown first for consistency, not platform preference.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure users.
- If possible, add a short note at the top indicating cross-platform compatibility.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No exclusive Windows tools, patterns, or missing Linux examples are present.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs in different sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Bash examples are intended for Linux/macOS users and PowerShell for Windows users to improve clarity.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in nearly every section, Bash (Linux/macOS) examples are presented before PowerShell (Windows) examples. There are no Windows-specific tools, patterns, or references that would disadvantage Linux users. The Azure CLI and Helm are cross-platform tools, and no steps require Windows-only features. The only minor bias is the ordering of Bash before PowerShell, which may slightly favor Linux users in terms of visibility.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to ensure equal visibility.
- Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS, and that users can choose either based on their preference.
- If possible, add a note clarifying that the Azure CLI and Helm commands work identically across platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used exclusively, and all commands are cross-platform (using Azure CLI and Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that both are equally supported.
- Add a note clarifying that all commands are cross-platform and can be run on Linux, macOS, and Windows.
- If possible, provide guidance for users running Azure CLI and Helm on macOS, such as installation links or troubleshooting tips.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but the PowerShell examples are always shown after Bash. There is no evidence of Windows-only tools or patterns being used, and all commands are based on the Azure CLI and Helm, which are cross-platform. However, the PowerShell examples are extensive and use Windows-style syntax, which may create a slight bias toward Windows users. There are no missing Linux examples, and Linux users can complete all tasks without friction.
Recommendations
- Consider adding a note clarifying that both Bash and PowerShell are fully supported and that the Azure CLI and Helm commands work identically on Linux, macOS, and Windows.
- If possible, provide a brief summary or table at the top indicating that users can choose either Bash or PowerShell, depending on their OS.
- Ensure that the Bash and PowerShell tabs are equally prominent and that Bash is not always shown first by default, or randomize the order to avoid subtle bias.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in feature and bug fix listings for both platforms. However, there is a consistent pattern of listing Windows download links and version numbers before Linux, and occasional references to Windows-specific tools (e.g., PowerShell, msiexec) in troubleshooting and known issues sections. There are no missing Linux examples or features, but Windows terminology and tools are sometimes mentioned without Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side to avoid implicit prioritization.
- When referencing Windows-specific tools or installation methods (e.g., msiexec, PowerShell), provide equivalent Linux instructions or clarify that the guidance is Windows-only.
- In troubleshooting sections, if a Windows-specific issue is described, consider adding a note about whether similar issues exist or do not exist on Linux.
- Where possible, use neutral language (e.g., 'For Windows, do X. For Linux, do Y.') to ensure both platforms are equally addressed.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively or before their Linux equivalents.
Recommendations
- Ensure both Bash and PowerShell tabs are equally prominent and accessible.
- Consider explicitly mentioning that Azure CLI commands work on Linux, macOS, and Windows.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS users, while PowerShell is for Windows users.
- If possible, provide a generic 'CLI' tab or clarify that Bash is the default for Linux/macOS.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via Azure CLI. No critical Linux/macOS gaps are present.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions are not Windows-centric (current screenshot is neutral).
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux/macOS examples are missing, and there is no exclusive mention of Windows tools or patterns.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is shown first for consistency, not preference.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance if Windows-specific steps are added.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd (cross-platform) is mentioned, SSMS is listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The examples for connecting use sqlcmd, which is available on both Windows and Linux, but there is no explicit Linux/macOS-specific guidance or mention of Linux GUI alternatives. The Azure CLI commands are cross-platform, but the overall tone and tool recommendations favor Windows users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit Linux/macOS connection instructions, including any prerequisites for installing sqlcmd on Linux/macOS.
- List sqlcmd as the primary example, or show both SSMS and sqlcmd examples equally.
- Add a note about how to install sqlcmd on Linux/macOS, or link to relevant installation documentation.
- Consider including screenshots or walkthroughs for Linux/macOS users where appropriate.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors and PowerShell. Linux installation instructions are less explicit (e.g., 'install curl package'), and there is a note about using cmd.exe instead of PowerShell for curl, but no equivalent Linux/macOS guidance. The documentation assumes familiarity with Windows environments and tools, creating minor friction for Linux/macOS users.
Recommendations
- List installation instructions for all platforms equally, and avoid always putting Windows first.
- Provide explicit Linux/macOS installation commands (e.g., 'sudo apt install curl' or 'brew install curl') instead of vague instructions.
- Add notes for Linux/macOS users where Windows-specific caveats are mentioned (e.g., clarify curl usage differences on Linux/macOS).
- Where PowerShell-specific notes are given, add equivalent Linux/macOS shell guidance.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' as the NTP server, 'sts.windows.net', 'servicebus.windows.net') and lists Windows NTP as the default in notes. Windows terminology and endpoints are mentioned before Linux equivalents, and Windows-specific URLs are present. However, Linux endpoints and requirements are also included (e.g., 'packages.microsoft.com' for Linux packages, 'linuxgeneva-microsoft.azurecr.io' for log collection). No examples or instructions are given that are Windows-only, and Linux requirements are not missing.
Recommendations
- Clarify that NTP can use Linux-based servers (e.g., 'pool.ntp.org') and provide guidance for both Windows and Linux environments.
- Avoid listing Windows-specific endpoints (e.g., 'time.windows.com') as the default; instead, mention both Windows and Linux options equally.
- Where Windows terminology is used (e.g., 'Windows NTP'), add equivalent Linux terminology or examples.
- Ensure that any references to Windows tools or endpoints are balanced with Linux alternatives, especially in notes and examples.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and sections are often presented first, and Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail. The cleanup script for removing stale resources is only provided in PowerShell, with no equivalent Bash or Azure CLI example for Linux users. Overall, Linux parity is strong, but Windows-centric tools and ordering create minor friction.
Recommendations
- Provide equivalent cleanup scripts or guidance for Linux users (e.g., Bash or Azure CLI examples) alongside PowerShell scripts.
- Where possible, present Windows and Linux instructions in parallel or alternate their ordering to avoid always showing Windows first.
- Add references to Linux-native automation tools (such as cron, systemd, or Ansible) for agent lifecycle management, similar to the Windows update infrastructure examples.
- Ensure that all Azure CLI and azcmagent command examples are clearly labeled as cross-platform.
- Consider including a summary table at the top showing parity of features and management tasks across Windows and Linux.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation consistently refers to Azure CLI installation and usage, but in the 'Management machine requirements' section, the Azure CLI installation link points to the Windows-specific install page first, and the text refers to 'Azure CLI x64' without clarifying OS parity. There are no explicit Linux/macOS examples or links, and no mention of Linux-specific requirements or considerations for the management machine, despite Azure CLI being cross-platform. No PowerShell or Windows-only tools are referenced, but the ordering and linking suggest a Windows-first bias.
Recommendations
- Update the 'Management machine requirements' section to clarify that Azure CLI is supported on Windows, Linux, and macOS, and provide install links for all platforms.
- Explicitly state that the management machine can be any supported OS (Windows, Linux, macOS) and provide guidance for Linux/macOS users.
- Add examples or notes for Linux/macOS users where relevant, such as file paths, CLI usage, or prerequisites.
- Avoid linking only to Windows install pages for cross-platform tools like Azure CLI.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation for `azcmagent connect` shows minor Windows bias by describing the interactive browser login as 'Windows only' and mentioning Windows certificate store options before Linux equivalents. The access token section references the Windows PowerShell cmdlet `Get-AzAccessToken` without mentioning Linux alternatives. However, Linux authentication methods are well-covered, and most examples are generic and applicable cross-platform.
Recommendations
- Add explicit Linux/macOS equivalents for obtaining access tokens (e.g., using Azure CLI: `az account get-access-token`).
- Clarify certificate authentication options for Linux (e.g., specify typical Linux certificate storage locations and usage patterns).
- Present authentication options in a platform-neutral order, or explicitly note Linux/macOS methods where relevant.
- Where Windows-specific tools (like PowerShell) are mentioned, also provide Linux/macOS alternatives.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux VM extensions for Azure Arc-enabled servers, listing both platforms' extensions in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, Portal, ARM templates) are mentioned without platform bias, and partner extensions are shown for both OSes. No critical Linux features are missing, and Linux examples are present where relevant.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side, to avoid implicit prioritization.
- Explicitly state that all deployment methods (CLI, PowerShell, Portal, ARM templates) are available for both Windows and Linux, and provide links to Linux-specific usage guides where possible.
- Ensure that any referenced 'additional information' links for Linux extensions are as comprehensive as their Windows counterparts.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Run command on Azure Arc-enabled servers, but Windows is listed first in the 'Operating Systems' section. There are no explicit Windows-only examples or tools, and Linux-specific notes are included. However, the page links to separate guides for Azure CLI, PowerShell, and REST API usage, which may have further bias but are not analyzed here.
Recommendations
- List operating systems in alphabetical order (e.g., 'Linux and Windows') to avoid subtle Windows-first bias.
- Ensure linked pages (CLI, PowerShell, REST) provide parity in examples for both Windows and Linux, including shell/script differences.
- Add explicit examples or notes highlighting Linux usage where relevant, such as shell script execution or command syntax differences.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but there are signs of Windows bias. Windows examples and log file paths are presented first, and PowerShell-specific commands are used for Windows, while Linux examples are given later. Windows-specific tools and paths (e.g., %ProgramData%, PowerShell, .exe invocation) are mentioned before their Linux equivalents. Some error codes reference Windows tools (e.g., PowerShell version requirements) without Linux analogs.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid always presenting Windows first.
- Where possible, provide Linux-specific troubleshooting tips alongside Windows-specific ones (e.g., for log file locations, permissions, and command syntax).
- Ensure error codes referencing Windows tools (like PowerShell) also mention Linux equivalents or clarify if not applicable.
- Use neutral language and structure (e.g., 'On Windows...' and 'On Linux...') instead of always starting with Windows.
- Highlight Linux log file paths and commands equally, and consider including macOS guidance if applicable.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed script and output, and references to Windows tools (PowerShell, IIS) appear before Linux equivalents. The 'Related content' section also mentions PowerShell before Azure CLI. Overall, Linux parity is maintained, but Windows is prioritized in ordering and tool references.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure equal detail and explanation for both PowerShell and Bash examples, including output screenshots.
- In 'Related content', mention Azure CLI before or alongside PowerShell to reflect cross-platform tooling.
- Where possible, reference Linux tools (e.g., Apache) alongside Windows tools (e.g., IIS) when discussing use cases.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. Windows/PowerShell examples and tools are sometimes mentioned before Linux equivalents, and PowerShell is highlighted as a primary automation option. However, Linux support is acknowledged throughout, and most features are described as available for both Windows and Linux VMs.
Recommendations
- Ensure Linux and macOS CLI examples are provided alongside PowerShell, especially in automation and onboarding sections.
- Mention Linux tools and workflows (e.g., Bash, shell scripting) equally when listing supported automation options.
- When referencing Azure Automation, clarify that Python runbooks and Linux management are fully supported.
- Review links and tabs to ensure Linux documentation is as prominent as Windows documentation.
- Where possible, alternate the order of Windows and Linux mentions to avoid 'Windows-first' perception.