docs: reword the final use case

Signed-off-by: Peter Fiddes <[email protected]>

content/docs/tutorials/certificate-defaults/README.md

@@ -37,10 +37,10 @@ By setting custom defaults across our cluster, we enable platform teams to tackl
 
     Use a `ClusterPolicy` to set a custom default value for the `spec.secretName` required field.
 
-- **To enable users to request a certificate by providing only one certificate identity field**
+- **Make application developers' lives easier by allowing them to create secure X.509 TLS certificates with the minimum of configuration.**
 
     Use a `ClusterPolicy` to set all other required `Certificate.spec` fields.
-    A `Certificate` resource user will then only need to supply a single specification field, one of:
+    Only a single identity specification field will be required, one of:
     - `commonName` or `literalSubject`
     - `dnsNames`
     - `uris`