[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

docs/development.rst

@@ -255,7 +255,7 @@ final deployment to PyPI_ can be done by creating a GitHub Release:
 #. Select the release tag that was just pushed, and set the release title to be the tag
    (e.g. ``v1.2.3``).
 #. Use the "Auto-generate release notes" button to generate a skeleton of the release
-   notes and then augment them with the preprepared release notes the release maintainer
+   notes and then augment them with the prepared release notes the release maintainer
    has written.
 #. Select "This is a pre-release" if the release is a release candidate.
 #. Select "Create a discussion for this release" if the release is a stable release.

docs/likelihood.rst

@@ -115,7 +115,7 @@ constraint terms are derived implicitly as each type of modifier
 unambiguously defines the constraint terms it requires. Correlated shape
 modifiers and normalisation uncertainties have compatible constraint
 terms and thus modifiers can be declared that *share* parameters by
-re-using a name [1]_ for multiple modifiers. That is, a variation of a
+reusing a name [1]_ for multiple modifiers. That is, a variation of a
 single parameter causes a shift within sample rates due to both shape
 and normalisation variations.