doc: Update documentation for TLS certs renewal

Recent crc releases know how to updated the TLS certs when needed, so we
should mention it, and document that it takes a while.

docs/source/getting-started/content/proc_troubleshooting-expired-certificates.adoc

@@ -1,12 +1,16 @@
 [id="troubleshooting-expired-certificates_{context}"]
 = Troubleshooting expired certificates
 
-Each released `{bin}` binary includes an embedded system bundle that expires 30 days after the release due to certificates embedded in the OpenShift cluster.
+Prior to {rh-prod} 1.2.0, the system bundle included in each released `{bin}` binary expired 30 days after the release due to certificates embedded in the OpenShift cluster.
 Using an older `{bin}` binary or system bundle will result in an expired certificates error.
 
+Starting from {prod} 1.2.0, the embedded certificates can be automatically renewed by {bin}.
+The certificate renewal process is triggered when needed when [command]`{bin} start` is run.
+When certificates need to be renewed, this can add up to five minutes to the start time of the cluster.
+
 .Procedure
 
-To resolve expired certificate errors:
+With {prod} releases older than 1.2.0, to resolve expired certificate errors:
 
 . link:{crc-download-url}[Download the latest {prod} release] and place the `{bin}` binary in your `$PATH`.