fixing some broken links

Signed-off-by: anaxceron <[email protected]>

docs/user-guide/api-mediation/upgrade-zowe-no-downtime.md

@@ -95,7 +95,7 @@ For more information, see the article _VARY TCPIP,,SYSPLEX_ in the IBM documenta
 
 4. Start the upgraded instance.
 
-    **Note:** For more information about stopping and starting instances, see [Starting and stopping Zowe](../start-zowe-zos.md).
+    **Note:** For more information about stopping and starting instances, see [Starting and stopping Zowe](./../start-zowe-zos.md).
 
 5. Wait until instance B is up and synchronized with instance A, wherein services are registered in all Discovery Services. To verify that instance B is up and sychronized with instance A, check the following accessibility conditions:
 

docs/user-guide/import-certificates.md

@@ -12,7 +12,7 @@ To import a PKCS12 certificate, it is first necessary to import a certificate au
 * [Manually import a certificate authority into a web browser](#manually-import-a-certificate-authority-into-a-web-browser)
 * [Import a local CA certificate on Linux](#import-a-local-ca-certificate-on-linux)
 
-Once you have imported your CA, you can configure the zowe.yaml according to [Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA](#certificate-configuration-scenarios.md/#scenario-2-use-a-pkcs12-keystore-and-import-a-certificate-generated-by-another-ca) described in the article Certificate configuration scenarios.
+Once you have imported your CA, you can configure the zowe.yaml according to [Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA](../user-guide/certificate-configuration-scenarios.md#scenario-2-use-a-file-based-pkcs12-keystore-and-import-a-certificate-generated-by-another-ca) described in the article Certificate configuration scenarios.
 
 For PKCS12 certificate users, specify the following parameters in the `zowe.yaml` file:
 
@@ -132,7 +132,7 @@ After successfully importing your local CA certificate on Linux, you can now [im
 
 ## Importing an existing JCERACFKS certificate
 
-To import a JCERACFKS certificate, use the example yaml according to [Scenario 4: Use a z/OS keyring-based keystore and connect to an existing certificate](#certificate-configuration-scenarios.md/#scenario-4-use-a-zos-keyring-and-connect-to-an-existing-certificate) in the article Certificate configuration scenarios.
+To import a JCERACFKS certificate, use the example yaml according to [Scenario 4: Use a z/OS keyring-based keystore and connect to an existing certificate](certificate-configuration-scenarios.md#scenario-4-use-a-zos-keyring-based-keystore-and-connect-to-an-existing-certificate) in the article Certificate configuration scenarios.
 
 To use a JCERACFKS certificate, specify the following parameters in the `zowe.yaml` file:
 
@@ -164,7 +164,7 @@ You can now use your imported JCERACFKS certificate. See [next steps](#next-step
 
 ## Importing a certificate stored in an MVS data set into a Zowe key ring
 
-To import a certificate that is stored in a data set into a key ring, configure the zowe.yaml according to the example yaml in [Scenario 5: Use a z/OS keyring-based keystore and import a certificate stored in a data set](#certificate-configuration-scenarios/#scenario-5-use-a-zos-keyring-and-import-a-certificate-stored-in-a-data-set)
+To import a certificate that is stored in a data set into a key ring, configure the zowe.yaml according to the example yaml in [Scenario 5: Use a z/OS keyring-based keystore and import a certificate stored in a data set](certificate-configuration-scenarios#scenario-5-use-a-zos-keyring-based-keystore-and-import-a-certificate-stored-in-a-data-set)
 
  To use a JCERACFKS certificate, specify the following parameters in the `zowe.yaml` file.
 

docs/user-guide/k8s-introduction.md

@@ -22,5 +22,5 @@ The Zowe containers are designed to be run together with extensions and Zowe uti
 * You may encounter an issue that some plugins are not showing up in Zowe Desktop. You can try the **Refresh Applications** icon showing up in Desktop start menu.
 * You may encounter an issue that some services are not showing up in Zowe API Catalog. You can try the **Refresh Static APIs** button showing up in upper-right corner of API Catalog web page.
 * `useConfigmgr` is disabled within containers, therefore yaml schema validation is not yet supported.
-* Containerization 2.10.x release still pending due to an issue related to app-server resulting to can't access the desktop, please use the [2.9.x documentation](../../../versioned_docs/version-v2.9.x/user-guide/k8s-introduction.md) instead.
+* Containerization 2.10.x release still pending due to an issue related to app-server resulting to can't access the desktop, please use the [2.9.x documentation](../../versioned_docs/version-v2.9.x/user-guide/k8s-introduction.md) instead.
 

versioned_docs/version-v2.10.x/user-guide/import-certificates.md

@@ -14,7 +14,7 @@ To import a PKCS12 certificate, it is first necessary to import a certificate au
 * [Manually import a certificate authority into a web browser](#manually-import-a-certificate-authority-into-a-web-browser)
 * [Import a local CA certificate on Linux](#import-a-local-ca-certificate-on-linux)
 
-Once you have imported your CA, you can configure the zowe.yaml according to [Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA](#certificate-configuration-scenarios.md/#scenario-2-use-a-pkcs12-keystore-and-import-a-certificate-generated-by-another-ca) described in the article Certificate configuration scenarios.
+Once you have imported your CA, you can configure the zowe.yaml according to [Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA](../user-guide/certificate-configuration-scenarios.md#scenario-2-use-a-file-based-pkcs12-keystore-and-import-a-certificate-generated-by-another-ca) described in the article Certificate configuration scenarios.
 
 For PKCS12 certificate users, specify the following parameters in the `zowe.yaml` file: