Run pre-commit and fix issues

Author: pedro-psb

README.md

@@ -43,11 +43,11 @@ pipx install git+https://github.com/pulp/pulp-docs --include-deps
 pulp-docs serve
 ```
 
-For development, use your prefered method!
+For development, use your preferred method!
 
 ## How to override `repolist.yml`
 
-If you want to share work you are doing in muliple forks, you can share a custom `repolist.yml` which points to your forks.
+If you want to share work you are doing in multiple forks, you can share a custom `repolist.yml` which points to your forks.
 
 Then, anyone can test them locally by overriting your `repolist.yml` like so:
 
@@ -63,4 +63,3 @@ repos:
 $ export PULPDOCS_MKDOCS_FILE="path/to/my/repolist.yml"
 $ pulp-docs serve
 ```
-

docs/dev/guides/create-plugin-overviews.md

@@ -30,5 +30,3 @@ Things to keep in mind:
 - **Audience:** Target newcomers. Experienced users will probably use the ToC or the search.
 - **Format:** Synopsis + Roadmap. Tell what your plugin is, what it does and a simple roadmap for starting.
 - **Size:** Keep it brief. This should an easy win for the user before he starts this journey.
-
-

docs/dev/index.md

@@ -8,4 +8,3 @@ Also, this is used for the production build.
 
 To start using it, see the [Getting Started](site:pulp-docs/docs/dev/tutorials/getting-started/) section.
 Before contributing, we recommend reading about the [Architecture](site:pulp-docs/docs/dev/reference/architecture/).
-

docs/dev/reference/markdown-cheatsheet.md

@@ -166,4 +166,3 @@ With subtitle:
 [See mkdocs-material](https://squidfunk.github.io/mkdocs-material/reference/admonitions/#supported-types)
 
 Use them wisely.
-

mkdocs.yml

@@ -38,7 +38,7 @@ theme:
       toggle:
         icon: material/toggle-switch
         name: Switch to light mode
-# Blog's Navigation needs to be excempt from literate nav...
+# Blog's Navigation needs to be exempt from literate nav...
 nav:
   - Home: "index.md"
   - "User Manual":

pulp_docs/blog/posts/2020/2020-07-09-pulp-3.5-installer-roles.md

@@ -10,7 +10,7 @@ There have been some big changes to Pulp Installer in 3.5.0, in terms of the Ans
 including breaking changes. Merely reading the release notes for individual changes does not paint
 a complete or clear picture, hence why we are writing this blog post.
 
-In short, we refactored the Pulp Installer roles to acheive an SOA (Service Oriented Architecture).
+In short, we refactored the Pulp Installer roles to achieve an SOA (Service Oriented Architecture).
 
 We now have 1 role for each service, and each can be installed to a server of its own.
 

pulp_docs/blog/posts/2020/2020-08-18-pulp-container-2.0-is-generally-available.md

@@ -36,7 +36,7 @@ As part of this release and throughout the different beta iterations, the follow
 * Fixed not being able to push tags with periods in them. [#6884](https://pulp.plan.io/issues/6884)
 * Fixed problem with the `client_max_body_size` value in the nginx config. [#6916](https://pulp.plan.io/issues/6916)
 * Refactored `token_authentication` so that it now happens in the `pulpcore-api` app. [#6894](https://pulp.plan.io/issues/6894)
-* Fixed a crash when trying to access content with an unparseable token. [#7124](https://pulp.plan.io/issues/7124)
+* Fixed a crash when trying to access content with an unparsable token. [#7124](https://pulp.plan.io/issues/7124)
 * Fixed a runtime error which was triggered when a registry client sends an accept header with an inappropriate media type for a manifest and the conversion failed. [7125](https://pulp.plan.io/issues/7125)
 * Updated the sync machinery to not store an image manifest as a tag’s artifact. [#6816](https://pulp.plan.io/issues/6816)
 * Added a validation, that a push repository cannot be distributed by specifying a version. [#7012](https://pulp.plan.io/issues/7012)

pulp_docs/blog/posts/2020/2020-08-28-august-community-update.md

@@ -103,6 +103,6 @@ participate in real-time. See the [triage process](https://docs.pulpproject.org/
 more details. You can also read through the [triage archives](https://logs.pulpproject.org/pulp-meeting/)
 * **Open Floor** - every Tuesday and Friday immediately after Bug Triage in #pulp-meeting on Freenode
 (IRC). It's a time for developer discussion, feedback, and decisions on code/issues/PRs/process
-relating to pulpcore or plugins. To particiapte, put a topic on
+relating to pulpcore or plugins. To participate, put a topic on
 [the agenda](https://hackmd.io/@pulp/triage/edit). Minutes will be sent to the pulp-dev mailing
 list.

pulp_docs/blog/posts/2021/2021-04-08-pulp-3.12-is-generally-available.md

@@ -8,7 +8,7 @@ tags:
 <!-- more -->
 Let's take a look at the main updates and enhancements as part of this release.
 
-This release also includes a plethora of bugfixes as well as some nice enhancements to Pulpcore and the Plugin API. For a full overview of changes, check out the [changlog](https://docs.pulpproject.org/pulpcore/changes.html).
+This release also includes a plethora of bugfixes as well as some nice enhancements to Pulpcore and the Plugin API. For a full overview of changes, check out the [changelog](https://docs.pulpproject.org/pulpcore/changes.html).
 
 ## Support added for automatic publishing and distributing [#7626](https://pulp.plan.io/issues/7626)
 
@@ -20,7 +20,7 @@ Pulp can prohibit or allow checksums by setting the `ALLOWED_CONTENT_CHECKSUMS`
 
 As part of this release, a number of validation steps have been added to help to ensure that you can debug and manage content checksums that are synched as part of the on-demand sync process.
 
-New documenation has been also added for the [ALLOWED_CONTENT_CHECKSUMS setting](https://docs.pulpproject.org/pulpcore/en/master/nightly/settings.html#allowed-content-checksums).
+New documentation has been also added for the [ALLOWED_CONTENT_CHECKSUMS setting](https://docs.pulpproject.org/pulpcore/en/master/nightly/settings.html#allowed-content-checksums).
 
 A new warning has been added to the on-demand sync process to check if remote artifacts are detected with checksums that do not correspond with the `ALLOWED_CONTENT_CHECKSUMS`. [#7985](https://pulp.plan.io/issues/7985)
 

pulp_docs/blog/posts/2021/2021-05-24-pulpcore-3.13-is-generally-available.md

@@ -37,6 +37,6 @@ You can view the [updated workflow](https://docs.pulpproject.org/pulpcore/workfl
 
 There are ongoing efforts to improve the tasking system so that it is specific to Pulp but agnostic to the queuing technology. With this release workers should no longer be started through **rq** but by the native command **pulpcore-worker**. This affects users who do manual installations of Pulp 3. For more specific instructions, see the [updated documentation](https://docs.pulpproject.org/pulpcore/installation/instructions.html#pypi-installation).
 
-For a full list of bug fixes and changes, see the [changlog](https://docs.pulpproject.org/pulpcore/changes.html).
+For a full list of bug fixes and changes, see the [changelog](https://docs.pulpproject.org/pulpcore/changes.html).
 
 For any questions, feel free to write to us on `[email protected]`.