fix: minor fixes

Signed-off-by: Henry Schreiner <henryfs@princeton.edu>

Author: henryiii

docs/pages/guides/gha_basic.md

@@ -53,14 +53,16 @@ you use a develop branch, you probably will want to include that. You can also
 specify specific branches for pull requests instead of running on all PRs (will
 run on PRs targeting those branches only).
 
-## Pre-commit
+## Prek / Pre-commit
 
-If you use [pre-commit][] (or [prek][]) in CI, you can run it directly in GitHub
+If you use [prek][] or [pre-commit][] in CI, you can run it directly in GitHub
 Actions. Prek is a faster Rust rewrite of pre-commit that supports most real
-world usage.
+world usage and supports the same configuraiton and hooks.
 
 {% tabs runner %} {% tab prek Prek %}
 
+Prek can run using the official action:
+
 ```yaml
 lint:
   name: Lint

docs/pages/guides/style.md

@@ -47,8 +47,6 @@ a custom pre-commit hook before; it's quite elegant and does not add or commit
 the changes, it just makes the changes and allows you to check and add them. You
 can always override the hook with `-n`.
 
-[pre-commit]: https://pre-commit.com
-
 {% rr PC100 %} Here is a minimal `.pre-commit-config.yaml` file with some handy
 options:
 
@@ -1047,6 +1045,8 @@ You also might like the following hook, which cleans Jupyter outputs:
 [schemastore]: https://schemastore.org
 [typos]: https://github.com/crate-ci/typos
 [typos-ref]: https://github.com/crate-ci/typos/blob/master/docs/reference.md
+[pre-commit]: https://pre-commit.com
+[prek]: https://prek.j178.dev
 
 <!-- prettier-ignore-end -->