Merge pull request #18 from felixfontein/cleanup

General cleanup

Author: felixfontein

content/en/docs/_index.md

@@ -51,13 +51,6 @@ Or whatever variation of the above fits your system and shell.
 To use **SOPS** as a library, take a look at the [decrypt
 package](https://pkg.go.dev/github.com/getsops/sops/v3/decrypt).
 
-::: sectnum
-:::
-
-::: contents
-Table of Contents
-:::
-
 # Usage
 
 For a quick presentation of SOPS, check out this Youtube tutorial:
@@ -196,10 +189,12 @@ environment variable as a comma separated list. The default order is
 If you want to test **SOPS** without having to do a bunch of setup, you
 can use the example files and pgp key provided with the repository:
 
-    $ git clone https://github.com/getsops/sops.git
-    $ cd sops
-    $ gpg --import pgp/sops_functional_tests_key.asc
-    $ sops edit example.yaml
+``` sh
+$ git clone https://github.com/getsops/sops.git
+$ cd sops
+$ gpg --import pgp/sops_functional_tests_key.asc
+$ sops edit example.yaml
+```
 
 This last step will decrypt `example.yaml` using the test private key.
 
@@ -304,11 +299,15 @@ projects/my-project/locations/global/keyRings/sops/cryptoKeys/sops-key ENCRYPT_D
 
 Now you can encrypt a file using:
 
-    $ sops encrypt --gcp-kms projects/my-project/locations/global/keyRings/sops/cryptoKeys/sops-key test.yaml > test.enc.yaml
+``` sh
+$ sops encrypt --gcp-kms projects/my-project/locations/global/keyRings/sops/cryptoKeys/sops-key test.yaml > test.enc.yaml
+```
 
 And decrypt it using:
 
-    $ sops decrypt test.enc.yaml
+``` sh
+$ sops decrypt test.enc.yaml
+```
 
 ## Encrypting using Azure Key Vault
 
@@ -358,7 +357,9 @@ is the client secret.
 Encrypting/decrypting with Azure Key Vault requires the resource
 identifier for a key. This has the following form:
 
-    https://${VAULT_URL}/keys/${KEY_NAME}/${KEY_VERSION}
+```
+https://${VAULT_URL}/keys/${KEY_NAME}/${KEY_VERSION}
+```
 
 To create a Key Vault and assign your service principal permissions on
 it from the commandline:
@@ -381,11 +382,15 @@ https://sops.vault.azure.net/keys/sops-key/some-string
 
 Now you can encrypt a file using:
 
-    $ sops encrypt --azure-kv https://sops.vault.azure.net/keys/sops-key/some-string test.yaml > test.enc.yaml
+``` sh
+$ sops encrypt --azure-kv https://sops.vault.azure.net/keys/sops-key/some-string test.yaml > test.enc.yaml
+```
 
 And decrypt it using:
 
-    $ sops decrypt test.enc.yaml
+``` sh
+$ sops decrypt test.enc.yaml
+```
 
 ## Encrypting and decrypting from other programs
 
@@ -661,8 +666,10 @@ example policy is shown below.
 You can specify a role in the `--kms` flag and `SOPS_KMS_ARN` variable
 by appending it to the ARN of the master key, separated by a **+** sign:
 
-    <KMS ARN>+<ROLE ARN>
-    arn:aws:kms:us-west-2:927034868273:key/fe86dd69-4132-404c-ab86-4269956b4500+arn:aws:iam::927034868273:role/sops-dev-xyz
+```
+<KMS ARN>+<ROLE ARN>
+arn:aws:kms:us-west-2:927034868273:key/fe86dd69-4132-404c-ab86-4269956b4500+arn:aws:iam::927034868273:role/sops-dev-xyz
+```
 
 ## AWS KMS Encryption Context
 
@@ -1326,14 +1333,8 @@ stores:
         indent: 2
 ```
 
-:::: note
-::: title
-Note
-:::
-
-The YAML emitter used by sops only supports values between 2 and 9. If
+Note: The YAML emitter used by sops only supports values between 2 and 9. If
 you specify 1, or 10 and larger, the indent will be 2.
-::::
 
 ## YAML anchors