Rolled back formatting on existing manual docs.

docs/install.md

@@ -299,10 +299,10 @@ This image can be pushed to a container registry and shipped independently. All
 
 The setup for Kubernetes is very similar to that for Docker, and requires a fairly minimal deployment or pod definition to function. There
 are a few options to mix and match, including a deployment without a cache file, a stateful set with a persistent cache, and a standalone
-unmanaged pod.
+unmanned pod.
 
-Deployment
-===
+
+=== "deployment"
     ```yaml
     apiVersion: apps/v1
     kind: Deployment
@@ -350,9 +350,7 @@ Deployment
         targetPort: 80
     ```
 
-
-Stateful set
-=== 
+=== "stateful set"
     ```yaml
     apiVersion: apps/v1
     kind: StatefulSet
@@ -393,9 +391,7 @@ Stateful set
               storage: 1Gi
     ```
 
-Pod
-===
-
+=== "pod"
     ```yaml
     apiVersion: v1
     kind: Pod
@@ -426,10 +422,7 @@ Pod
 
 Configuration is relatively straightforward. As an example, a minimal configuration is provided.
 
-
-Resource definition
-=== 
-
+=== "resource definition"
     ```yaml
     apiVersion: v1
     kind: ConfigMap
@@ -441,19 +434,11 @@ Resource definition
         base-url: https://ntfy.sh
     ```
 
-
-from-file
-=== 
-
+=== "from-file"
     ```bash
     kubectl create configmap ntfy --from-file=server.yml 
     ```
 
-Kustomize-based deployment with persistent storage and Traefik ingress
-===
-
-Kustomize allows for deploying templated configurations in easy way
-
 ### Kustomization
 Create new folder, name it nfty and create kustomization.yaml within along all resources listed below. 
 Ingress is optional - you can skip this one if planning to expose service using different service type (hash it out from kustomization file)