corrected the hyperlink for component certs (#362)

Author: ptyagii

migration/nonRBACToRBAC/mtlsLdap/README.md

@@ -65,7 +65,7 @@ exit
 In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates.
 
 
 ## Deploy configuration secrets

migration/nonRBACToRBAC/mtlsOAuth/README.md

@@ -46,7 +46,7 @@ kubectl get pods -n confluent
 In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates.
 
 
 ## Deploy configuration secrets

migration/nonRBACToRBAC/mtlsOnly/README.md

@@ -34,11 +34,10 @@ kubectl get pods -n confluent
 In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../../assets/certs/component-certs/README.md) to generate these certificates.
 
 
 ## Deploy configuration secrets
-
 You'll use Kubernetes secrets to provide credential configurations.
 
 With Kubernetes secrets, credential management (defining, configuring, updating)

security/mds-mtls-c3-sso/README.md

@@ -53,7 +53,7 @@ kubectl get pods -n confluent
 In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates.
 
 ## Deploy configuration secrets
 

security/mds-mtls-with-vault/README.md

@@ -161,7 +161,7 @@ cat /tmp/fileUserPassword.txt | base64 | vault kv put /secret/fileuser.txt fileu
 In this scenario, you'll configure authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates.
 
 ## Deploy configuration secrets
 

security/mtls-rbac-with-sso-oauth/README.md

@@ -53,7 +53,7 @@ kubectl get pods -n confluent
 In this scenario, you'll configure internal authentication using the mTLS mechanism. With mTLS, Confluent components and clients use TLS certificates for authentication. The certificate has a CN that identifies the principal name.
 
 Each Confluent component service should have its own TLS certificate. In this scenario, you'll
-generate a server certificate for each Confluent component service. Follow [these instructions](../assets/certs/component-certs/README.md) to generate these certificates.
+generate a server certificate for each Confluent component service. Follow [these instructions](../../assets/certs/component-certs/README.md) to generate these certificates.
 
 ## Deploy configuration secrets