docs: Fix some typos (#13509)

Minor fixes I came across while reading the docs.

Release Notes:

- N/A
This commit is contained in:
Gilles Peiffer 2024-06-25 16:58:11 +02:00 committed by GitHub
parent f40d2313fb
commit b014f9f017
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 8 deletions

View File

@ -41,7 +41,7 @@ We plan to set aside time each week to pair program with contributors on promisi
Zed is made up of several smaller crates - let's go over those you're most likely to interact with:
- [`gpui`](/crates/gpui) is a GPU-accelerated UI framework which provides all of the building blocks for Zed. **We recommend familiarizing yourself with the root level GPUI documentation**
- [`gpui`](/crates/gpui) is a GPU-accelerated UI framework which provides all of the building blocks for Zed. **We recommend familiarizing yourself with the root level GPUI documentation.**
- [`editor`](/crates/editor) contains the core `Editor` type that drives both the code editor and all various input fields within Zed. It also handles a display layer for LSP features such as Inlay Hints or code completions.
- [`project`](/crates/project) manages files and navigation within the filetree. It is also Zed's side of communication with LSP.
- [`workspace`](/crates/workspace) handles local state serialization and groups projects together.

View File

@ -2,7 +2,7 @@
## Folder-specific settings
Folder-specific settings are used to override Zed's global settings for files within a specific directory in the project panel. To get started, create a `.zed` subdirectory and add a `settings.json` within it. It should be noted that folder-specific settings don't need to live only a project's root, but can be defined at multiple levels in the project hierarchy. In setups like this, Zed will find the configuration nearest to the file you are working in and apply those settings to it. In most cases, this level of flexibility won't be needed and a single configuration for all files in a project is all that is required; the `Zed > Settings > Open Local Settings` menu action is built for this case. Running this action will look for a `.zed/settings.json` file at the root of the first top-level directory in your project panel. If it does not exist, it will create it.
Folder-specific settings are used to override Zed's global settings for files within a specific directory in the project panel. To get started, create a `.zed` subdirectory and add a `settings.json` within it. It should be noted that folder-specific settings don't need to live only at a project's root, but can be defined at multiple levels in the project hierarchy. In setups like this, Zed will find the configuration nearest to the file you are working in and apply those settings to it. In most cases, this level of flexibility won't be needed and a single configuration for all files in a project is all that is required; the `Zed > Settings > Open Local Settings` menu action is built for this case. Running this action will look for a `.zed/settings.json` file at the root of the first top-level directory in your project panel. If it does not exist, it will create it.
The following global settings can be overridden with a folder-specific configuration:
@ -46,7 +46,7 @@ Here are all the currently available settings.
**Options**
1. To disable autosave, set it to `off`
1. To disable autosave, set it to `off`:
```json
{
@ -110,9 +110,9 @@ The name of any font family installed on the user's system
**Options**
Zed supports all OpenType features that can be enabled, disabled or set a value to a font feature for a given buffer or terminal font.
Zed supports all OpenType features that can be enabled or disabled for a given buffer or terminal font, as well as setting values for font features.
For example, to disable ligatures and set `7` to `cv01` for a given font you can add the following to your settings:
For example, to disable ligatures and set `cv01` to `7` for a given font you can add the following to your settings:
```json
{
@ -201,19 +201,19 @@ List of `string` values
"current_line_highlight": "none"
```
2. Highlight the gutter area.
2. Highlight the gutter area:
```json
"current_line_highlight": "gutter"
```
3. Highlight the editor area.
3. Highlight the editor area:
```json
"current_line_highlight": "line"
```
4. Highlight the full line.
4. Highlight the full line:
```json
"current_line_highlight": "all"