Cyclecloud
354
Total Pages
325
Linux-Friendly Pages
29
Pages with Bias
8.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
52 issues found
Showing 26-50 of 52 flagged pages
Cyclecloud
Download Cluster Projects and Templates
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays mild Windows bias by highlighting Microsoft HPC Pack (a Windows-centric job scheduler) prominently among the available templates, including a direct link to a PowerShell-based overview. No Linux-specific tools are given priority, and the HPC Pack entry is the only one with a link to a Microsoft documentation page, while others link to their respective open-source or vendor sites. There are no explicit Linux command examples or references to Linux-specific configuration patterns.
Recommendations
- Provide equivalent documentation links for Linux-based schedulers (e.g., Slurm, Grid Engine, HTCondor) to balance the prominence given to HPC Pack.
- Include example usage or configuration snippets for both Windows and Linux environments, especially for template import and management.
- Avoid giving exclusive or first mention to Windows tools; present all scheduler options in a neutral order or group by platform.
- Add notes or sections clarifying platform compatibility (Windows/Linux) for each template, and offer guidance for Linux users where appropriate.
Create Pull Request
Cyclecloud
Plan your CycleCloud Workspace for Slurm Deployment
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tools and patterns. It exclusively references Azure Bastion, VPN Gateway, and ExpressRoute for network access, which are primarily managed through Azure Portal or PowerShell, with no mention of Linux-native alternatives or CLI-based workflows. There are no examples or guidance for Linux users (e.g., SSH tunneling, OpenVPN, or Linux command-line tools), nor are Linux-specific deployment or access patterns discussed.
Recommendations
- Add examples and instructions for accessing CycleCloud Workspace for Slurm from Linux environments, such as SSH tunneling or OpenVPN.
- Include CLI-based workflows using Azure CLI and Linux shell commands alongside or before Azure Portal/PowerShell instructions.
- Mention Linux-native tools and patterns for network access and management (e.g., SSH, scp, rsync) where appropriate.
- Provide parity in documentation by ensuring that Linux and Windows users have clear, step-by-step guidance for all major deployment and access scenarios.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/staging-resources.md
...articles/cyclecloud/common-issues/staging-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on Azure CycleCloud resource staging issues but does not provide any platform-specific examples or troubleshooting steps. However, it references the Azure portal UI (which is most commonly accessed from Windows environments) and omits any command-line examples (such as Azure CLI or PowerShell), nor does it mention Linux tools or workflows. The lack of Linux-specific guidance or parity in examples constitutes a subtle Windows bias.
Recommendations
- Add Azure CLI examples for checking and configuring Storage Account hierarchical namespace and permissions, which are platform-agnostic and widely used on Linux.
- Include PowerShell examples if relevant, but ensure they are presented alongside equivalent Azure CLI commands.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform tools.
- Describe how to access and modify Storage Account settings using command-line tools, not just the Azure portal UI.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cluster-references/environment-reference.md
...cyclecloud/cluster-references/environment-reference.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Azure-centric, focusing exclusively on Azure Resource Manager (ARM) templates and related constructs. There are no examples or references to Linux-specific tools, deployment patterns, or cross-platform considerations. All examples use Azure-native paths and features, with no mention of Linux command-line tools, shell scripting, or non-Windows workflows.
Recommendations
- Add examples showing how to interact with CycleCloud and ARM templates using Linux shell commands (e.g., curl, az CLI in bash).
- Include references or links to Linux-friendly tools and scripting patterns for managing templates and deployments.
- Explicitly mention cross-platform compatibility and provide guidance for users working from Linux environments.
- If relevant, provide parity in documentation for Linux-based automation (e.g., using bash scripts to upload templates, manage resources, etc.).
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/azure-credentials.md
...articles/cyclecloud/common-issues/azure-credentials.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation provides instructions using the Azure CLI, which is cross-platform, but all credential update steps reference the Azure portal (a web UI) and do not mention Linux-specific tools or command-line alternatives for credential management. There are no explicit Linux shell examples or guidance for users who may prefer or require non-GUI workflows.
Recommendations
- Add Linux shell (bash) command-line examples for updating credentials, such as using az CLI commands in bash.
- Explicitly mention that Azure CLI is cross-platform and provide instructions for installing and using it on Linux.
- Include guidance for users who may not have access to the Azure portal GUI, such as headless server environments.
- Ensure parity by referencing both Windows and Linux workflows where applicable.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/unavailable-sku.md
...n/articles/cyclecloud/common-issues/unavailable-sku.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references UI navigation steps (e.g., 'Settings', 'Azure types') without clarifying whether these are for the Azure Portal, a Windows-specific tool, or cross-platform. There are no CLI-based examples (such as Azure CLI or PowerShell), and no Linux-specific guidance or parity is provided. The absence of command-line examples or explicit Linux instructions may disadvantage Linux users.
Recommendations
- Add Azure CLI examples for checking available VM sizes and regions (e.g., using 'az vm list-sizes' or 'az vm list-skus').
- Clarify whether the instructions refer to the Azure Portal (which is cross-platform) or a Windows-only tool.
- If PowerShell examples are added, ensure equivalent Azure CLI (Linux-friendly) commands are also provided.
- Explicitly mention that the Azure Portal is accessible from any OS, if that is the intended interface.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/updating-scalesets.md
...rticles/cyclecloud/common-issues/updating-scalesets.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes resolving quota issues using graphical tools (Cluster page UI, Azure portal), which are more commonly used in Windows environments. There are no examples or instructions for performing these checks or quota requests using command-line tools (such as Azure CLI), which are preferred in Linux workflows.
Recommendations
- Add instructions for checking VM quotas using Azure CLI (az vm list-usage, az quota commands) with example commands.
- Include steps for requesting quota increases via CLI or REST API, not just through the portal.
- Ensure that both GUI and CLI methods are presented, with CLI examples given equal prominence.
- Mention that the CLI methods work cross-platform (Windows, Linux, macOS).
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by highlighting Microsoft HPC Pack (a Windows-specific job scheduler) in the template table, including a direct link to a PowerShell-based overview for HPC Pack, and referencing Windows tools before Linux equivalents. There are no explicit Linux command examples, but most templates are cross-platform or Linux-oriented. The documentation does not provide Linux-specific instructions or examples, and the only scheduler with a Microsoft/Windows focus (HPC Pack) is given prominence with a PowerShell documentation link.
Recommendations
- Add explicit Linux command-line examples (e.g., bash, shell) for template import and management alongside any Windows/PowerShell instructions.
- Ensure that Linux-oriented schedulers (Slurm, HTCondor, OpenPBS, Grid Engine) are given equal prominence, with direct links to their documentation and usage guides.
- Avoid linking to Windows/PowerShell documentation before Linux equivalents; provide both or alternate their order.
- Include notes or sections on platform compatibility and any differences in usage between Windows and Linux environments.
- Where possible, provide parity in tooling references, ensuring Linux tools (e.g., bash scripts, Linux CLI) are mentioned and demonstrated.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/add-node-array.md
...blob/main/articles/cyclecloud/how-to/add-node-array.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide explicit Windows or PowerShell examples, but it does lack Linux-specific command-line examples or references. The only CLI example uses the CycleCloud CLI, which is cross-platform, but there is no mention of Linux-specific workflows, tools, or shell commands. There are also no references to Linux editors or environment considerations, and the template editing instructions are generic. The absence of Linux-specific guidance or examples may make the documentation less accessible to Linux users.
Recommendations
- Add explicit Linux shell command examples for editing and importing the cluster template (e.g., using nano, vim, or cat for editing).
- Clarify that the CycleCloud CLI commands work on Linux, macOS, and Windows, and provide example commands for each platform if there are differences.
- Mention common Linux tools or workflows for managing template files (e.g., using bash scripts for automation).
- If there are any platform-specific prerequisites or behaviors (such as file paths or permissions), document them explicitly.
- Consider including screenshots or terminal output from a Linux environment to improve parity.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/plan-your-deployment.md
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tools and patterns, such as Azure Bastion, VPN Gateway, and Azure-specific networking constructs, without mentioning or providing guidance for Linux-native or open-source alternatives. There are no examples or instructions for Linux command-line tools, SSH, or cross-platform access methods, and all access scenarios assume Azure-native solutions.
Recommendations
- Provide examples or mention how to access CycleCloud Workspace for Slurm using standard SSH from Linux or macOS clients, not just via Azure Bastion or VPN Gateway.
- Include guidance for users who may want to use open-source VPN solutions (e.g., OpenVPN, WireGuard) instead of Azure VPN Gateway.
- Clarify whether Linux users can use native tools (e.g., SSH, SCP) to connect to the environment, and provide instructions or references.
- If possible, add a section or note on cross-platform access patterns, ensuring that both Windows and Linux users are supported equally.
- Mention any Linux-specific prerequisites or considerations for deploying or managing the environment.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-arm.md
...cs/blob/main/articles/cyclecloud/how-to/install-arm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias by mentioning Windows users and their shell options before Linux users, and by not providing explicit Linux-specific examples or instructions. While the Azure CLI is cross-platform and the SSH key generation is shown with Unix-style commands, Linux-specific guidance is minimal and often referenced only via external links. There are no PowerShell-specific examples, but the structure and order of instructions prioritize Windows users.
Recommendations
- Present Linux and Windows shell options in parallel, rather than listing Windows first.
- Provide explicit Linux (and macOS) instructions for shell access, such as using the default terminal or bash.
- Include Linux-specific examples and troubleshooting tips directly in the documentation, rather than linking out.
- Clarify that all CLI commands work on both Windows and Linux, and note any OS-specific differences if they exist.
- Consider adding a short section or callout for macOS users as well, to ensure parity across all major platforms.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/htcondor.md
...s/azure-docs/blob/main/articles/cyclecloud/htcondor.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally presents a Linux-centric workflow (CentOS images, Linux paths, Linux commands) but includes Windows-specific configuration options and paths in the configuration reference table. In several cases, Windows equivalents are mentioned after Linux defaults, and some options are marked as Windows-only. However, there are no explicit PowerShell or Windows command-line examples, and the primary usage examples are Linux-based.
Recommendations
- Provide explicit examples for both Linux and Windows environments where configuration paths or behaviors differ (e.g., show both /mnt/condor_data and C:\All Services\condor_local in context).
- Clarify in each configuration option table entry when a setting is platform-specific, and group or label them accordingly.
- If Windows is supported for HTCondor on CycleCloud, include at least one end-to-end example using a Windows image and relevant commands.
- Ensure that any Windows-only options (such as htcondor.ignore_hyperthreads) are clearly separated or highlighted to avoid confusion.
- Consider adding a section summarizing platform-specific considerations for both Linux and Windows users.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', Windows Server URNs, and 'Windows 2022 DataCenter' labels) while omitting equivalent Linux examples. Although the supported image table lists both Linux and Windows images, the usage examples and guidance focus exclusively on Windows, with no demonstration of Linux image configuration.
Recommendations
- Include Linux-based examples alongside Windows examples for specifying images, such as 'cycle.image.ubuntu22' or 'Alma Linux 8'.
- Alternate the order of examples or provide parallel examples for both Windows and Linux to avoid implicit prioritization.
- Add explicit guidance or notes for Linux users, such as how to specify Ubuntu or SLES images, and any Linux-specific considerations.
- Ensure that documentation sections referencing image configuration provide equal coverage for both Windows and Linux operating systems.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/slurm-3.md
...cs/azure-docs/blob/main/articles/cyclecloud/slurm-3.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows/Azure bias. It exclusively references Azure-specific tools (e.g., azslurm CLI, CycleCloud), and all examples and workflows are built around these tools. There are no references to native Linux tools or generic Slurm commands outside the Azure context. While all command-line examples use bash and Slurm commands (which are Linux-native), the documentation assumes the use of Azure CycleCloud and its tooling, which is primarily designed for Azure (and often managed from Windows environments). There are no PowerShell examples, but the documentation does not mention or provide parity for non-Azure Linux environments or tools.
Recommendations
- Add examples and instructions for using standard Slurm commands and workflows outside of the Azure/CycleCloud context, to help users familiar with generic Linux/Slurm environments.
- Clarify which steps are Azure/CycleCloud-specific and which are standard Slurm operations, possibly providing side-by-side examples.
- Mention and, where possible, provide guidance for users running Slurm on native Linux environments without Azure CycleCloud.
- If possible, reference or link to documentation for running Slurm on non-Azure platforms to provide context and alternatives.
- Ensure that Linux-native tools and workflows are not overshadowed by Azure-specific tooling, and explain any differences in behavior or configuration.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The release notes mention Windows Server 2019/2022 and HPC Pack 2019 support before Linux equivalents. Windows-specific tools (HPC Pack) are highlighted, while Linux features (e.g., Slurm, Ubuntu 22) are mentioned later and with less detail. No Linux/macOS-specific examples or parity notes are provided.
Recommendations
- List Linux and Windows support/features together, or alternate their order to avoid Windows-first bias.
- Provide equal detail for Linux features (e.g., mention supported distributions and versions for Slurm clusters).
- Include notes/examples for Linux/macOS users where relevant, such as installation instructions or supported tools.
- Explicitly state Linux/macOS compatibility for new features where applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Windows image examples first in all code samples and lists Windows images before Linux images in the table. While Linux images are supported and mentioned, the ordering and example selection prioritize Windows, which may subtly signal a Windows-centric approach.
Recommendations
- Alternate or randomize the order of example OS images in code samples, showing Linux first in some cases.
- Provide explicit Linux image examples alongside Windows ones in all code blocks.
- List Linux images before Windows images in tables, or group by OS type.
- Add a note clarifying equal support for Linux and Windows images.
Cyclecloud
Download Cluster Projects and Templates
...main/articles/cyclecloud/download-cluster-templates.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Microsoft HPC Pack (a Windows-only scheduler) and linking to a Windows PowerShell documentation page for its overview. While most templates and examples are cross-platform, the only external documentation link provided is for a Windows tool, and it appears before Linux-native schedulers in the template list.
Recommendations
- Add equivalent documentation links for Linux-native schedulers (e.g., Slurm, HTCondor, Grid Engine) alongside the HPC Pack link.
- Ensure that Linux and macOS tools are described and linked with equal prominence as Windows tools.
- Consider ordering the template list alphabetically or by popularity, rather than placing Windows tools first.
- Provide explicit notes about platform compatibility for each scheduler/template.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally platform-neutral in its configuration examples, focusing on Azure CycleCloud's INI-style configuration files. However, there is a subtle Windows bias in the 'Devices' section, where Azure Logical Unit Numbers (LUNs) are mentioned and linked to a PowerShell module without referencing Linux equivalents (such as device naming conventions or tools like lsblk or /dev/sd*). Additionally, the documentation refers to Azure portal UI concepts (e.g., 'blade'), which are not platform-specific but are more familiar to Windows users. Linux-specific tools and workflows (such as LVM commands, mounting via /etc/fstab, or filesystem utilities) are only briefly mentioned in the configuration options table and not illustrated with examples.
Recommendations
- Provide explicit Linux examples for device assignment and mounting, such as referencing /dev/sdX naming or using lsblk to identify devices.
- Include sample Linux shell commands for formatting and mounting volumes (e.g., mkfs, mount, fstab entries).
- Add a section or note clarifying how device assignment and mounting differ on Linux versus Windows, including relevant tools and commands.
- Balance references to Azure PowerShell modules with Azure CLI or Linux-native tools.
- Ensure that configuration examples are accompanied by both Windows and Linux context where applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 (a Windows-only HPC solution) before mentioning Linux-related features. Windows tools and platforms are referenced explicitly, while Linux equivalents are mentioned later or not at all. No Linux-specific examples or tools are highlighted, and the order of presentation favors Windows technologies.
Recommendations
- List Linux distributions and features alongside or before Windows equivalents (e.g., mention Ubuntu 22 support before Windows Server).
- Highlight Linux HPC solutions (such as Slurm, OpenPBS, or GridEngine) with equal prominence as Windows HPC Pack.
- Include explicit references to Linux tools, commands, or workflows where relevant.
- Ensure that documentation examples and feature lists are balanced between Windows and Linux platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Windows image examples first in all code samples and lists Windows images before Linux equivalents in the example configurations. However, it does include Linux images in the supported images table and mentions Linux operating systems as available options.
Recommendations
- Provide example code snippets for both Windows and Linux images, alternating which is shown first.
- Explicitly show Linux image configuration examples alongside Windows examples.
- Balance the order of image listings and examples to avoid consistently prioritizing Windows.
- Add notes or sections clarifying Linux-specific considerations if any exist.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 before Linux-specific features. Windows tools (HPC Pack) are highlighted, while Linux equivalents are not mentioned. Although Ubuntu 22 support for Slurm is noted, Windows features are listed first and more prominently.
Recommendations
- List Linux and Windows features in parallel or alternate order to avoid Windows-first impression.
- Mention Linux equivalents to Windows tools (e.g., OpenHPC, Slurm, GridEngine) when referencing Windows-specific tools like HPC Pack.
- Provide explicit examples or notes for both Windows and Linux where relevant, especially for new features.
- Highlight improvements for Linux distributions (e.g., RHEL, CentOS) alongside Ubuntu.
Cyclecloud
Download Cluster Projects and Templates
...main/articles/cyclecloud/download-cluster-templates.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Microsoft HPC Pack (a Windows-specific scheduler) and linking to a PowerShell-based overview for it. The HPC Pack is listed second in the table, ahead of several Linux-native schedulers. However, the main CLI example is cross-platform, and most templates/projects listed are Linux-oriented.
Recommendations
- Clarify that the CycleCloud CLI is cross-platform and works on Linux/macOS as well as Windows.
- When mentioning HPC Pack, note its Windows specificity and provide equivalent Linux scheduler options (e.g., Slurm, Grid Engine) with equal prominence.
- Avoid linking to Windows/PowerShell documentation without Linux alternatives or context.
- Consider ordering template types so Linux-native schedulers are not consistently listed after Windows tools.
Cyclecloud
Install the Command Line Interface
...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides installation instructions for both Linux and Windows, but Windows-specific tools (PowerShell, Windows Explorer) are described in more detail and with GUI steps. Windows prerequisites (Python install) are mentioned before Linux, and Windows installation instructions use PowerShell scripts and GUI actions, whereas Linux instructions use standard shell commands. The Linux section is functional, but Windows examples and tools are given more prominence and detail.
Recommendations
- Provide equivalent command-line installation instructions for Windows (e.g., using Command Prompt or PowerShell commands to extract and run the installer), not just GUI steps.
- Mention Linux installation steps first or present both platforms in parallel for parity.
- Include notes for macOS users if supported, or clarify platform support.
- Offer a Windows command-line example for adding the CLI to PATH, similar to the Linux export example.
- Balance the level of detail and guidance between Windows and Linux sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page displays a mild Windows bias, particularly in the Active Directory section, where Windows-centric terminology and examples (DOMAIN\user, AD server, Windows sign-in patterns) are presented first and exclusively. There is no explicit mention of Linux equivalents (e.g., sAMAccountName vs. UPN, Linux LDAP client usage), and the examples assume a Windows environment for authentication patterns. However, the LDAP and Entra ID sections are more neutral and mention Linux clusters and SSH keys, providing some parity.
Recommendations
- Include Linux-specific examples for Active Directory authentication, such as UPN formats and typical Linux client configuration steps.
- Clarify that both Windows and Linux clients can authenticate, and provide examples for each (e.g., 'DOMAIN\user' for Windows, 'user@domain.com' for Linux).
- Add notes or links to documentation on configuring Linux systems to use Active Directory or LDAP for authentication.
- Ensure that screenshots and instructions do not assume a Windows-only environment, and mention cross-platform compatibility where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents Windows and Linux paths and behaviors in parallel, but there is a slight Windows-first bias in some sections (e.g., installation paths listed with Windows first). There is one notable case where a command ('jetpack run_on_shutdown') is explicitly unsupported on Windows, but no equivalent Windows example or workaround is provided. Most command examples use generic syntax applicable to both platforms, but Linux-specific features (bash scripts, udev rules) are mentioned without Windows alternatives.
Recommendations
- Present Linux and Windows paths and instructions in parallel, alternating which platform is listed first.
- Where commands are Linux-only (e.g., 'jetpack run_on_shutdown'), clarify Windows alternatives or explicitly state that no equivalent exists.
- For features that differ between platforms (e.g., HealthCheck 'forever' option), provide clear tables or callouts summarizing platform differences.
- Include PowerShell or Windows batch script examples where Linux bash scripts are shown, or explain why such functionality is not available on Windows.
- Ensure references to system tools (e.g., udev) mention Windows equivalents or clarify their absence.