docs: fix intersphinx links

2i2c-org · Jan 9, 2024 · aa10066 · aa10066
1 parent 7995fc7
commit aa10066
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/contributing/code-review.md b/docs/contributing/code-review.md
@@ -3,7 +3,7 @@
 
 Much of our active infrastructure is configured and automatically updated via CI/CD pipelines.
 This means that changes in this repository often immediately impact the infrastructure that we run.
-As such, we follow team policies for review/merge that are more specific [than our general development merge policies](tc:development:merge-policy).
+As such, we follow team policies for review/merge that are more specific [than our general development merge policies](inv:tc#development:merge-policy).
 
 This document codifies our guidelines for doing code review and merging pull requests on active infrastructure (ie, anything in the `infrastructure/` codebase).
 

diff --git a/docs/topic/access-creds/secrets.md b/docs/topic/access-creds/secrets.md
@@ -50,7 +50,7 @@ For example, if a service we use has become compromised, and we need to generate
 To rotate our secrets, take these steps:
 
 1. Determine which configuration file you'd like to update. See [](secrets:locations).
-2. Unencrypt the configuration file. See [the team compass documentation](tc:secrets:sops) for instructions on unencrypting.
+2. Unencrypt the configuration file. See [the team compass documentation](inv:tc#secrets:sops) for instructions on unencrypting.
 3. Generate a new key with `openssl`:
 
    ```