Fix and improve docs (#13620)

<!--
Thank you for contributing to uv! To help us out with reviewing, please
consider the following:

- Does this pull request include a summary of the change? (See below.)
- Does this pull request include a descriptive title?
- Does this pull request include references to any relevant issues?
-->

## Summary

I follow the advices from the IDE spell checker and grammar checker, fix
some typos, and improve the docs.

docs/concepts/projects/config.md

@@ -124,7 +124,7 @@ with the default build system.
 Build systems are used to power the following features:
 
 - Including or excluding files from distributions
-- Editable install behavior
+- Editable installation behavior
 - Dynamic project metadata
 - Compilation of native code
 - Vendoring shared libraries

docs/concepts/projects/sync.md

@@ -202,7 +202,7 @@ while building a Docker image. `uv sync` has several flags for this purpose.
 - `--no-install-workspace`: Do not install any workspace members, including the root project
 - `--no-install-package <NO_INSTALL_PACKAGE>`: Do not install the given package(s)
 
-When these options are used, all of the dependencies of the target are still installed. For example,
+When these options are used, all the dependencies of the target are still installed. For example,
 `--no-install-project` will omit the _project_ but not any of its dependencies.
 
 If used improperly, these flags can result in a broken environment since a package can be missing

docs/concepts/projects/workspaces.md

@@ -50,7 +50,7 @@ the workspace context.
 
 Every workspace needs a root, which is _also_ a workspace member. In the above example, `albatross`
 is the workspace root, and the workspace members include all projects under the `packages`
-directory, with the exception of `seeds`.
+directory, except `seeds`.
 
 By default, `uv run` and `uv sync` operates on the workspace root. For example, in the above
 example, `uv run` and `uv run --package albatross` would be equivalent, while