Deployed 56349e5 to v0.7.4 with MkDocs 1.5.3 and mike 1.1.2

v0.7.4/more/development/index.html

@@ -4698,11 +4698,9 @@
 <div class="language-bash highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a>pnpm<span class="w"> </span>lint
 </span></code></pre></div>
 <h2 id="code-formatting-with-pre-commit-hooks">Code formatting with pre-commit hooks</h2>
-<p>To ensure a consistent style and formatting across the project source, the project utilizes Git <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks"><code>pre-commit</code></a> hooks to perform some formatting and linting before a commit is allowed.
-That way, everyone uses the same style and some common issues can be caught early on.</p>
-<p>Once installed, hooks will run when you commit. If the formatting isn't quite right or a linter catches something, the commit will be rejected.
-You'll need to look at the output and fix the issue. Some hooks will format failing files, so all you need to do is <code>git add</code> those files again
-and retry your commit.</p>
+<p>To ensure a consistent style and formatting across the project source, the project utilizes Git <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks"><code>pre-commit</code></a> hooks to perform some formatting and linting before a commit is allowed.</p>
+<p>Once installed, hooks will run when you commit. If the formatting isn't quite right, the commit will be rejected and you'll need to look at the output and fix the issue. Most hooks will automatically format failing files, so all you need to do is <code>git add</code> those files again and retry your commit.</p>
+<p>See the <a href="https://pre-commit.com/#install">pre-commit documentation</a> to get started.</p>
 <h2 id="service-widget-guidelines">Service Widget Guidelines</h2>
 <p>To ensure cohesiveness of various widgets, the following should be used as a guide for developing new widgets:</p>
 <ul>