docs: Link to backup process

content/docs/installation/helm.md

@@ -240,8 +240,8 @@ Drawbacks:
 
 ### helm installation
 
-cert-manager *does not use* the [official helm method](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/ )
-of installing CRD resources. This is because this method makes upgrading CRDs
+cert-manager **does not use** the [official helm method](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/ )
+of installing CRD resources. This is because it makes upgrading CRDs
 impossible with `helm` CLI alone. The helm team explain the limitations
 of their approach [here](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations).
 
@@ -252,8 +252,9 @@ upgraded with your cert-manager release when you use
 that if you uninstall the release, the CRDs will also be uninstalled. If that
 happens then you will loose all instances of those CRDs, e.g. all `Certificate`
 resources in the cluster. You should consider if this is likely to happen to
-you and have a mitigation, such as backups or a means to reapply resources
-from an Infrastructure as Code (IaC) pattern.
+you and have a mitigation, such as
+[backups](https://cert-manager.io/docs/tutorials/backup/#backing-up-cert-manager-resource-configuration)
+or a means to reapply resources from an Infrastructure as Code (IaC) pattern.
 
 **Note** this also means a typo like `installCRD: true` would be an invalid
 value and helm would silently ignore this and remove the CRDs when you next