style: pre-commit fixes

Author: pre-commit-ci[bot]

docs/faqs.md

@@ -5,10 +5,10 @@ This section covers common needs.
 ## Starting a new project
 
 The easiest way to get started is to use the [Scientific Python cookie][], which
-makes a new project following the [Scientific Python Development Guidelines][]. Scikit-build-core
-is one of the backends you can select. The project will have a lot of tooling prepared
-for you as well, including pre-commit checks and a noxfile; be sure to read the guidelines
-to see what is there and how it works.
+makes a new project following the [Scientific Python Development Guidelines][].
+Scikit-build-core is one of the backends you can select. The project will have a
+lot of tooling prepared for you as well, including pre-commit checks and a
+noxfile; be sure to read the guidelines to see what is there and how it works.
 
 Another option is the [pybind11 example][].
 
@@ -78,8 +78,8 @@ automatically does this for you. See [repairing](#repairing-wheels).
 
 ## Making a Conda recipe
 
-`scikit-build-core` is available on conda-forge, and is used in [dozens
-of recipes][]. There are a few things to keep in mind.
+`scikit-build-core` is available on conda-forge, and is used in [dozens of
+recipes][]. There are a few things to keep in mind.
 
 You need to recreate your `build-system.requires` in the `host` table, with the
 conda versions of your dependencies. You also need to add `cmake` and either

docs/getting_started.md

@@ -1,10 +1,10 @@
 # Getting started
 
 If you've never made a Python package before, [packaging.python.org's
-tutorial][] is a great place to start. It walks you through creating a simple package
-in pure Python using modern tooling and configuration. Another great resource is
-the [Scientific Python Developer Guide][]. And a tutorial can be found at
-[INTERSECT Training: Packaging][].
+tutorial][] is a great place to start. It walks you through creating a simple
+package in pure Python using modern tooling and configuration. Another great
+resource is the [Scientific Python Developer Guide][]. And a tutorial can be
+found at [INTERSECT Training: Packaging][].
 
 ## Quick start
 

docs/overrides.md

@@ -2,9 +2,9 @@
 
 Scikit-build-core has an override system, similar to cibuildwheel and mypy. You
 specify a `tool.scikit-build.overrides` array with an `if` key. That `if` key
-can take several values, including several based on [PEP 508][]. Inside the override,
-you can set any value `tool.scikit-build` supports, and it will override if the `if`
-condition is true.
+can take several values, including several based on [PEP 508][]. Inside the
+override, you can set any value `tool.scikit-build` supports, and it will
+override if the `if` condition is true.
 
 ## If conditions
 
@@ -110,8 +110,8 @@ The value of `sys.implementation.name`. Takes a regex. Some common values:
 
 ### `implementation-version` (version)
 
-Derived from `sys.implementation.version`, following [PEP 508][]. Takes a specifier
-set. This is the PyPy version on PyPy, for example.
+Derived from `sys.implementation.version`, following [PEP 508][]. Takes a
+specifier set. This is the PyPy version on PyPy, for example.
 
 ### `env.*` (string or bool)