What problem(s) was I solving?

The documentation had inconsistent code formatting and outdated command examples that could confuse users. Specifically:

• The JSON comment syntax was using block comment style (/* */) instead of line comment style (//) which is more appropriate for JSONc files
• The command example was using npx humanlayer when the tool is now installed directly via brew
• The code block wasn't properly syntax-highlighted

What user-facing changes did I ship?

• Updated the settings.json example to use proper JSONc comment syntax (// instead of /* */)
• Simplified the humanlayer launch command from npx humanlayer to humanlayer to reflect current installation method
• Added proper syntax highlighting to the bash command block for better readability

How I implemented it

Made three targeted changes to docs/introduction.mdx:

1. Changed the comment style in the settings.json example from block comments to line comments for JSONc consistency
2. Updated the humanlayer launch command to remove the npx prefix since users install via brew now
3. Added bash language identifier to the code block for proper syntax highlighting

How to verify it

Manual Testing

• View the rendered documentation to ensure formatting appears correct
• Verify the JSONc comment syntax is highlighted properly
• Confirm the bash command block has proper syntax highlighting
• make check passes (note: unrelated type errors in humanlayer-wui exist)
• make test passes (note: unrelated integration test failures in hld exist)

Description for the changelog

docs: improve code formatting and update command examples in introduction