7322f09934
Based on my analysis of the git diff and documentation changes, I can now provide the summary:
## Documentation Update Summary
### Changes Made
| File | Change | Related Code |
| --- | --- | --- |
| docs/src/configuring-languages.md | Removed extraneous blank line in Storage Location list | Prettier formatting fix |
| docs/src/configuring-zed.md | Removed extraneous blank line in preview tabs list | Prettier formatting fix |
| docs/src/development.md | Removed 2 extraneous blank lines in numbered workflow steps | Prettier formatting fix |
| docs/src/extensions/themes.md | Removed 5 extraneous blank lines in Theme object components list | Prettier formatting fix |
| docs/src/languages/r.md | Removed extraneous blank line in extension list | Prettier formatting fix |
| docs/src/vim.md | Removed extraneous blank line in AnyQuotes/AnyBrackets section | Prettier formatting fix |
### Rationale
These changes are formatting-only fixes to comply with Prettier's 80-character line width standard defined in `docs/.prettierrc`. The blank lines that were removed appeared between list item headers and their nested content, which Prettier considers unnecessary. All changes maintain the same rendered output - only the source markdown structure is affected.
### Review Notes
- All 6 files now pass `npx prettier --check docs/src/`
- No content changes - purely whitespace/formatting normalization
- Changes involve removing blank lines between numbered/bulleted list items and their sub-items (e.g., `2. **Test the first version:**` followed by a blank line before the nested bullets)
- This is a formatting consistency fix, not triggered by specific code changes
- Total impact: 11 line deletions across 6 files
Triggered by: commit 12dbbdd1d3
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.