diff --git a/content/advanced/migrating-repos.md b/content/advanced/migrating-repos.md
index 2d0b656..4a3fcd4 100644
--- a/content/advanced/migrating-repos.md
+++ b/content/advanced/migrating-repos.md
@@ -47,7 +47,7 @@ Here's an explanation of some fields on the [Gitea migration page](https://codeb
 - **Access Token**: You will paste the access token generated here. An access token is required to migrate metadata.
 - **Migration Items**: Here you can select the metadata you want migrated.
 
-<h2 id=starting-migration>Starting Migration</h2>
+<h2 class="content-title" id=starting-migration>Starting Migration</h2>
 
 Once you've filled out all the fields, click the `Migrate Repository` button.
 Migration might take a while, depending on how large the repo is.
diff --git a/content/collaborating/citable-code.md b/content/collaborating/citable-code.md
index 2983144..9e8e9ba 100644
--- a/content/collaborating/citable-code.md
+++ b/content/collaborating/citable-code.md
@@ -11,7 +11,7 @@ The third option, which actually complements the second, is to assign a [Digital
 
 This page will show you how to do just that. The process can be decomposed in four steps.
 
-<h2 id="creating-a-release"> Create a release of your repository</h2>
+<h2 class="content-title" id="creating-a-release"> Create a release of your repository</h2>
 Creating a release is optional but recommended. The reason is simply that a release will make it explicit what version of your code you want to share/cite. Any further edits to your code will not be included in the release. In other words, it is good practice to share/cite a release with fixed code rather than the always changing code of your repository.
 
 To create a release, first go to the `Releases` tab of your repository, and click on `New Release`:
diff --git a/content/security/gpg-key.md b/content/security/gpg-key.md
index b65d10d..7420550 100644
--- a/content/security/gpg-key.md
+++ b/content/security/gpg-key.md
@@ -19,7 +19,7 @@ If you have your public key in an easy to find location, great! You can skip to
 > **IMPORTANT**   
 > Be sure that your selected key uses the same email as your Codeberg account.
 
-<h2 id=Generating>Generating a GPG key</h2>
+<h2 class="content-title" id=Generating>Generating a GPG key</h2>
 If you haven’t already, be sure to [install](https://gnupg.org/download/index.html#binary) GnuPG, as you will be using it to generate your keys.
 
 1. Type `gpg --full-generate-key` into your terminal
@@ -30,7 +30,7 @@ If you haven’t already, be sure to [install](https://gnupg.org/download/index.
 6. Enter your information, be sure to use the same email as your Codeberg account
 7. Type in a passphrase, make sure you write it down somewhere safe. You'll need it later to add your key to Git or revoke it if it is compromised
 
-<h2 id=Adding-to-Codeberg>Adding your GPG key to Codeberg</h2>
+<h2 class="content-title" id=Adding-to-Codeberg>Adding your GPG key to Codeberg</h2>
 
 1. Type `gpg --list-secret-keys --keyid-format LONG` into the terminal
 2. Select the key you would like to use (the one you just generated). In this example, the GPG key ID is `3AA5C34371567BD2`:
@@ -47,7 +47,7 @@ ssb   rsa4096/42B317FD4BA89E7A 2021-06-06 [E] [expires: 2022-06-06]
 4. Copy the output including the `-----BEGIN PGP PUBLIC KEY BLOCK-----` and `-----END PGP PUBLIC KEY BLOCK-----`
 5. Go to the [SSH/GPG Keys tab](https://codeberg.org/user/settings/keys) in your Codeberg settings.
 6. Click `Add Key` in the `Manage GPG Keys` section, paste in your public key and click the `Add Key` button.
-<h2 id=Adding-to-git>Telling Git about your GPG key</h2>
+<h2 class="content-title" id=Adding-to-git>Telling Git about your GPG key</h2>
 In order for you to use your key you will also need to tell Git about it.
 
 1. Open your terminal