Fix pre code in guides

content/guides/devto.md

@@ -20,22 +20,32 @@ After posting, copy the link to the post.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the post copied above):
 
-`proof@metacode.biz=https://dev.to/USERNAME/POST_TITLE`
+```
+proof@metacode.biz=https://dev.to/USERNAME/POST_TITLE
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified dev.to account.

content/guides/discourse.md

@@ -20,22 +20,32 @@ After posting, copy the link to your profile page (it should end with your **/u/
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to replace PROFILE_URL with the link to the profile copied above):
 
-`proof@metacode.biz=PROFILE_URL`
+```
+proof@metacode.biz=PROFILE_URL
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Discourse account.

content/guides/dns.md

@@ -16,20 +16,32 @@ No specific TTL value is required.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to replace DOMAIN, don't include https://):
 
-`proof@metacode.biz=dns:DOMAIN?type=TXT`
+```
+proof@metacode.biz=dns:DOMAIN?type=TXT
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
+
+And you're done! Reload your profile page, it should now show a verified domain name.

content/guides/encrypt.md

@@ -10,7 +10,9 @@ The idea is that you use someone's public key to encrypt a message. From then on
 
 If you already have a public key (or its fingerprint) you would like to use to encrypt a message, great! If not, you could use the following fingerprint:
 
-`9f0048ac0b23301e1f77e994909f6bd6f80f485d`
+```
+9f0048ac0b23301e1f77e994909f6bd6f80f485d
+```
 
 ## Encrypt a message
 

content/guides/gitea.md

@@ -28,22 +28,32 @@ After creating the project, copy the link to the project.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the project copied above):
 
-`proof@metacode.biz=https://gitea.example.com/USERNAME/gitea_proof`
+```
+proof@metacode.biz=https://gitea.example.com/USERNAME/gitea_proof
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Gitea account.

content/guides/github.md

@@ -22,22 +22,32 @@ After creating a public gist, copy the link to the gist.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the post copied above):
 
-`proof@metacode.biz=https://gist.github.com/USERNAME/12345678912345678912345678912345`
+```
+proof@metacode.biz=https://gist.github.com/USERNAME12345678912345678912345678912345
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Github account.

content/guides/gitlab.md

@@ -30,22 +30,32 @@ After creating the project, copy the link to the project.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the project copied above):
 
-`proof@metacode.biz=https://gitlab.example.com/USERNAME/gitlab_proof`
+```
+proof@metacode.biz=https://gitlab.example.com/USERNAME/gitlab_proof
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified GitLab account.

content/guides/hackernews.md

@@ -20,22 +20,32 @@ This is an OpenPGP proof that connects my OpenPGP key to this Hackernews account
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to replace USERNAME):
 
-`proof@metacode.biz=https://news.ycombinator.com/user?id=USERNAME`
+```
+proof@metacode.biz=https://news.ycombinator.com/user?id=USERNAME
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Hackernews account.

content/guides/lobsters.md

@@ -18,22 +18,32 @@ This is an OpenPGP proof that connects my OpenPGP key to this Lobste.rs account.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to replace USERNAME):
 
-`proof@metacode.biz=https://lobste.rs/u/USERNAME`
+```
+proof@metacode.biz=https://lobste.rs/u/USERNAME
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Lobste.rs account.

content/guides/managing-proofs-deleting.md

@@ -6,40 +6,58 @@ Over time, you may need to delete proofs. Changing proofs can be achieved by del
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Launch the notation prompt:
 
-`notation`
+```
+notation
+```
 
 Enter the 'none' notation to delete all notations:
 
-`none`
+```
+none
+```
 
 Save the changes:
 
-`save`
+```
+save
+```
 
 ## Delete one of your proofs
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Launch the notation prompt:
 
-`notation`
+```
+notation
+```
 
 Enter the **-** (minus) symbol followed by the proof you want to delete. Make sure you type the proof exactly like it is in your key.
 
-`-proof@metacode.biz=dns:yourdomain.org?type=TXT`
+```
+-proof@metacode.biz=dns:yourdomain.org?type=TXT
+```
 
 _To make it easier to enter the right proof, you could first [list all proofs](managing-proofs-listing) and simply copy the proof (including "proof@metacode.biz=") you want to delete._
 
 Save the changes:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```

content/guides/managing-proofs-key.md

@@ -6,11 +6,15 @@ Let's list the identity proofs stored in our OpenPGP keys.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 List detailed preferences:
 
-`showpref`
+```
+showpref
+```
 
 You should now see your key details, uid, and proofs assigned to your keys:
 
@@ -26,4 +30,6 @@ You should now see your key details, uid, and proofs assigned to your keys:
 
 Exit gpg:
 
-`quit`
+```
+quit
+```

content/guides/managing-proofs-listing.md

@@ -6,11 +6,17 @@ Let's list the identity proofs stored in our OpenPGP keys.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+`
+```
+gpg --edit-key FINGERPRINT
+```
 
 List detailed preferences:
 
-`showpref`
+```
+showpref
+```
 
 You should now see your key details, uid, and proofs assigned to your keys:
 
@@ -26,4 +32,6 @@ You should now see your key details, uid, and proofs assigned to your keys:
 
 Exit gpg:
 
-`quit`
+```
+quit
+```

content/guides/mastodon.md

@@ -14,22 +14,32 @@ Add a new item under **Profile metadata** with the label **OpenPGP** and your PG
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update the link):
 
-`proof@metacode.biz=https://INSTANCE.ORG/@USERNAME`
+```
+proof@metacode.biz=https://INSTANCE.ORG/@USERNAME
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Mastodon account.

content/guides/pixelfed.md

@@ -18,24 +18,34 @@ This is an OpenPGP proof that connects my OpenPGP key to this Pixelfed account.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update the link):
 
-`proof@metacode.biz=https://INSTANCE.ORG/users/USERNAME`
+```
+proof@metacode.biz=https://INSTANCE.ORG/users/USERNAME
+```
 
 Please note that the **/users/** part of the URL is mandatory for the proof to work.
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Fediverse account (Pixelfed is part of the [Fediverse](#https://en.wikipedia.org/wiki/Fediverse)).

content/guides/pleroma.md

@@ -18,24 +18,34 @@ This is an OpenPGP proof that connects my OpenPGP key to this Pleroma account. F
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update the link):
 
-`proof@metacode.biz=https://INSTANCE.ORG/users/USERNAME`
+```
+proof@metacode.biz=https://INSTANCE.ORG/users/USERNAME
+```
 
 Please note that the **/users/** part of the URL is mandatory for the proof to work.
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Fediverse account (Pleroma is part of the [Fediverse](#https://en.wikipedia.org/wiki/Fediverse)).

content/guides/reddit.md

@@ -20,22 +20,32 @@ After posting, copy the link to the post.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the post copied above):
 
-`proof@metacode.biz=https://www.reddit.com/user/USERNAME/comments/123123/TITLE/`
+```
+proof@metacode.biz=https://www.reddit.com/user/USERNAME/comments/123123/TITLE/
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Reddit account.

content/guides/twitter.md

@@ -20,22 +20,32 @@ After posting, copy the link to the tweet.
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to update with the link to the tweet copied above):
 
-`proof@metacode.biz=https://twitter.com/USERNAME/status/1234567891234567891`
+```
+proof@metacode.biz=https://twitter.com/USERNAME/status/1234567891234567891
+```
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a verified Twitter account.

content/guides/verify.md

@@ -46,13 +46,17 @@ Sometimes, you want to know if a specific person or public key was used to creat
 
 Copy the following fingerprint:
 
-`653909A2F0E37C106F5FAF546C8857E0D8E8F074`
+```
+653909A2F0E37C106F5FAF546C8857E0D8E8F074
+```
 
 Paste it in the **Email / key id / fingerprint** field under **Public Key (3: HKP server)** and press the big button again. It could not be verified. Guess it wasn't Wiktor who signed that message.
 
 Now, copy the following fingerprint:
 
-`9f0048ac0b23301e1f77e994909f6bd6f80f485d`
+```
+9f0048ac0b23301e1f77e994909f6bd6f80f485d
+```
 
 Paste it in the same field and press the big button again. It did verify! It was Yarmo all along.
 

content/guides/web-key-directory.md

@@ -22,7 +22,9 @@ The LOCALPART above is actually the username hashed using the SHA-1 algorithm an
 
 So if you wish to make your key available as **jimothy@dm.com**, according to the [small utility](/util/wkd), the URL would become:
 
-`https://dm.com/.well-known/openpgpkey/hu/n9utc41qty791upt63rm5xtiudabmw6m`
+```
+https://dm.com/.well-known/openpgpkey/hu/n9utc41qty791upt63rm5xtiudabmw6m
+```
 
 ## The Advanced setup
 
@@ -36,7 +38,9 @@ Indeed, quite similar to the Direct setup, except for the **openpgpkey** subdoma
 
 The public key for **jimothy@dm.com** would be available at:
 
-`https://openpgpkey.dm.com/.well-known/openpgpkey/hu/dm.com/n9utc41qty791upt63rm5xtiudabmw6m`
+```
+https://openpgpkey.dm.com/.well-known/openpgpkey/hu/dm.com/n9utc41qty791upt63rm5xtiudabmw6m
+```
 
 ## WKD-as-a-service
 

content/guides/xmpp.md

@@ -18,25 +18,35 @@ This is an OpenPGP proof that connects my OpenPGP key to this XMPP account. For
 
 First, edit the key (make sure to replace FINGERPRINT):
 
-`gpg --edit-key FINGERPRINT`
+```
+gpg --edit-key FINGERPRINT
+```
 
 Add a new notation:
 
-`notation`
+```
+notation
+```
 
 Enter the notation (make sure to replace XMPP-ID):
 
-`proof@metacode.biz=xmpp:XMPP-ID`
+```
+proof@metacode.biz=xmpp:XMPP-ID
+```
 
 The XMPP-ID looks something like an email address: **user@domain.org**.
 
 Save the key:
 
-`save`
+```
+save
+```
 
 Upload the key to WKD or use the following command to upload the key to [keys.openpgp.org](https://keys.openpgp.org) (make sure to replace FINGERPRINT):
 
-`gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT`
+```
+gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
+```
 
 And you're done! Reload your profile page, it should now show a XMPP account.
 
@@ -50,6 +60,8 @@ If your XMPP identity proof is verified, a QR code is shown. Anyone can scan thi
 
 Making this identity proof yourself can be a tad difficult when using clients like Gajim, but luckily for us, [Conversations](https://conversations.im/) can directly generate the proof by going to **Account details > Share > Share as XMPP URI**. The resulting URI should look something like:
 
-`xmpp:user@domain.org?omemo-sid-123456789=A1B2C3D4E5F6G7H8I9...`
+```
+xmpp:user@domain.org?omemo-sid-123456789=A1B2C3D4E5F6G7H8I9...
+```
 
 To take advantage of the easy and secure XMPP identity proof including OMEMO fingerprints, follow the **basic edition** guide above but replace XMPP-ID with the URI obtained through the **Conversations** app.