(DOCSP-7018): Updated delete resource known issue. (#93)

* (DOCSP-7018): Updated delete resource known issue.

* Updated per @mongomoe review.

Author: atsansone

Makefile

@@ -36,7 +36,7 @@ help:
 
 ## Builds this branch's HTML under build/<branch>/html
 html:
-	time giza make html
+	giza make html
 
 
 #################################################################
@@ -46,7 +46,7 @@ html:
 ## Build this branch's HTML files to a fresh build directory
 clean-html:
 	rm -rf build/${GIT_BRANCH}
-	time giza make html
+	giza make html
 
 
 #################################################################

source/reference/known-issues.txt

@@ -10,16 +10,18 @@ Known Issues in the |k8s-op-full|
    :depth: 1
    :class: singlecol
 
-Disable Backups before Deleting a Resource
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Deleting a Resource with Backups Removes All Snapshots
+------------------------------------------------------
 
-When deleting a resource that has backup configured, you must disable backup first.
+When you delete a resource that has backup configured, the
+|k8s-op-short| terminates all backups. Deleting a resource removes all
+existing snapshots without warning.
 
 Configure Persistent Storage Correctly
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------------------
 
 If there are no
-`persistent volumes <https://kubernetes.io/docs/concepts/storage/persistent-volumes/>`__
+:k8sdocs:`persistent volumes </concepts/storage/persistent-volumes/>`
 available when you create a resource, the resulting |k8s-pod| stays in
 transient state and the Operator fails  (after 20 retries) with the
 following error:
@@ -30,15 +32,15 @@ following error:
 
 To prevent this error, either:
 
-- Provide `persistent volumes <https://kubernetes.io/docs/concepts/storage/persistent-volumes/>`__ or
+- Provide |k8s-pvs| or
 - Set ``persistent : false`` for the resource
 
 For testing only, you may also set ``persistent : false``. This
 *must not be used in production*, as data is not preserved between
 restarts.
 
 Remove Resources before Removing |k8s|
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------------------
 
 Sometimes |onprem| can diverge from |k8s|. This mostly occurs when
 |k8s| resources are removed manually. |onprem| can keep displaying an
@@ -49,7 +51,7 @@ resource specification to delete resources first so no dead Automation
 Agents remain.
 
 Create Separate Namespaces for |k8s-op-short| and MongoDB Resources
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------------------------------------------------------
 
 The best strategy is to create |k8s-op-short| and its resources in
 different namespaces so that the following operations would work
@@ -71,7 +73,7 @@ This would mean that it could not clean the configurations, which
 would have to be done in the |application|.
 
 Difficulties with Updates
-~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------------
 
 In some cases, the |k8s-op-short| can stop receiving change events. As
 this problem is hard to reproduce, the recommended workaround is to
@@ -90,14 +92,14 @@ automatically and starts working correctly:
       :doc:`Kubernetes Operator installation </tutorial/install-k8s-operator>`
 
 Machine Memory vs. Container Memory
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-----------------------------------
 
 MongoDB versions older than 3.6.13, 4.0.9, and 4.1.9 report host system RAM, not
 container RAM.
 
 
 Changes to Avoid
-~~~~~~~~~~~~~~~~
+----------------
 
 The |k8s-op-short| will not be able to apply the following change on a MongoDB Deployment simultaneously: