diff --git a/docs/kb.md b/docs/kb.md
index 1ab98a37f..950487842 100644
--- a/docs/kb.md
+++ b/docs/kb.md
@@ -58,9 +58,9 @@ There are some cases where it had to delete the StatefulSet and re-install a new
 
 4. Delete StatefulSet application and associated PVCs.
 
-   ​    
+   
 
-5. Create a new PVC YAML named *newPVC.yaml* with same configuration. Specify old PV name belongs to volumename under the PVC spec.
+5. Create a new PVC YAML named *newPVC.yaml* with same configuration. Specify old PV name belongs to *volumeName* under the PVC spec.
 
    ```
    apiVersion: v1
@@ -133,11 +133,13 @@ There are some cases where it had to delete the StatefulSet and re-install a new
    mongo-persistent-storage-mongo-0   Bound     pvc-cc6767b4-52e8-11e9-b1ef-42010a800fe7   5G         RWO            mongo-pv-az    5m
    ```
 
+   
+
 10. Apply the same StatefulSet application YAML. The pod will come back online by re-using the existing PVC. The application pod status can be get by following command.
 
-    ```
-    kubectl get pods -n <namespace>
-    ```
+   ```
+   kubectl get pods -n <namespace>
+   ```
 
    
 
diff --git a/website/versions.json b/website/versions.json
index b0e330288..74e40c04f 100644
--- a/website/versions.json
+++ b/website/versions.json
@@ -1,6 +1,7 @@
 {
   "versions": {
-      "0.8.1": ["latest", "https://docs.openebs.io"],
+      "0.8.2": ["latest", "https://docs.openebs.io"],
+	  "0.8.1": ["v0.8.1", "https://v081-docs.openebs.io"],
       "0.8.0": ["v0.8", "https://v08-docs.openebs.io"],
       "0.7.0": ["v0.7", "https://v07-docs.openebs.io"],
       "0.6.0": ["v0.6", "https://v06-docs.openebs.io"],