Update documentation/modules/pvc-naming-vmware-specific-template.adoc

Author: anarnold97

documentation/modules/pvc-naming-vmware-specific-template.adoc

@@ -64,7 +64,7 @@ The example above uses `regexReplaceAll` and `toLower` functions which might be
 
 * *PVC Name Restrictions*: PVC names generated by templates must adhere to the Kubernetes DNS-1123 label format. This is enforced during validation because PVC names are often reused as Kubernetes labels in other parts of the codebase. Templates that produce whitespace-only or excessively long output (e.g., over 57 characters if `pvcNameTemplateUseGenerateName` is set to `true`) will fail validation.
 
-* *Validation and Error Reporting*: {project-short} now validates the PVC name template earlier in the process using information from the plan’s VM inventory. Any template errors will be detailed in the plan conditions and logged, allowing for quicker identification and troubleshooting.
+* *Validation and Error Reporting*: {project-short} now validates the PVC name template earlier in the process using information from the plan’s VM inventory. Any template errors are detailed in the plan conditions and logged, allowing for quicker identification and troubleshooting.
 
 * *Uniqueness of PVC Names*: If `pvcNameTemplateUseGenerateName` is set to `false`, it is crucial to ensure that your PVC naming template generates unique names to avoid conflicts during migration.