docs: fix tildes (#1198)

docs/guide/commands/add.md

@@ -73,7 +73,7 @@ Added packagename @ file:///path/to/packagename as regular dependency
 
 * `--pre`: Include pre-releases when finding a package version
 
-* `--pin <PIN>`: Overrides the pin operator [possible values: `equal`, `tilde-equal``, `greater-than-equal``]
+* `--pin <PIN>`: Overrides the pin operator [possible values: `equal`, `tilde-equal`, `greater-than-equal`]
 
 * `--sync`: Runs `sync` automatically even if auto-sync is disabled.
 
@@ -83,4 +83,4 @@ Added packagename @ file:///path/to/packagename as regular dependency
 
 * `-q, --quiet`: Turns off all output
 
-* `-h, --help`: Print help (see a summary with '-h')
+* `-h, --help`: Print help (see a summary with `-h`)

docs/guide/commands/build.md

@@ -46,12 +46,12 @@ By default you will find the artifacts in the `dist` folder.
 
 * `-o, --out <OUT>`: An output directory (defaults to `workspace/dist`)
 
-* `--pyproject <PYPROJECT_TOML>`: Use this `pyproject.toml`` file
+* `--pyproject <PYPROJECT_TOML>`: Use this `pyproject.toml` file
 
 * `-c, --clean`: Clean the output directory first
 
 * `-v, --verbose`: Enables verbose diagnostics
 
 * `-q, --quiet`: Turns off all output
 
-* `-h, --help`: Print help
+* `-h, --help`: Print help

docs/guide/faq.md

@@ -102,7 +102,7 @@ accommodating to portable builds there are various limitations still with this
 approach.  One of them is that built Python distributions capture some absolute
 paths and other build-time configuration.  These file paths are then often used
 by build tools to invoke C compilers.  For instance you might run into a compiler
-error like ``error: stdio.h: No such file or directory`` when building C
+error like `error: stdio.h: No such file or directory` when building C
 extensions.  There is no known solution to this problem today other than
 [registering a non portable toolchain](toolchains/index.md#registering-toolchains).