Fixing broken links

Author: OlufunkeMoronfolu

content/en/docs/deployment/mendix-cloud-deploy/certificates/_index.md

@@ -96,6 +96,27 @@ To upload a certificate authority, follow these steps:
 
 1. Upload a certificate authority in the PEM format.
 
+## Frequently Asked Questions
+
+### Can You Create a `*.mycompany.com` Wildcard Certificate? {#wildcard}
+
+Yes. For [application-level certificates](/developerportal/deploy/application-level-certificates/), a wildcard certificate can only be used within the environments of a single app. This is because the private key is stored securely and cannot be accessed outside the app.
+
+To reuse a wildcard certificate across multiple apps or environments, Mendix Admins can create a central certificate in [Certificate Management](/control-center/certificate-management/). Central certificates can then be selected by Technical Contacts across different apps and environments.
+
+Technical Contacts can select the same wildcard certificate for different environments of the same app by using it with different subdomains. For example, `test.mycompany.com`, `accp.mycompany.com`, and `app.mycompany.com`.
+
+### How Do You Construct an Intermediate Certificate Chain Properly?
+
+Your certificate is signed by a certificate authority (CA) using the CA's intermediate certificate. The intermediate certificate is signed with the CA’s root certificate.
+
+To reach the root certificate, you must link your certificate through the intermediate certificate chain, usually just one intermediate certificate. Occasionally, a CA requires multiple intermediate certificates.
+
+* For application-level certificates, you provide the intermediate certificate chain when uploading the certificate at the application level
+* For central certificates, the chain is uploaded by the Mendix Admin
+
+You do not need to provide the root certificate, because every web browser has it in its trusted keystore.
+
 ## Read More
 
 * [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security)

content/en/docs/deployment/mendix-cloud-deploy/certificates/application-level-certificates.md

@@ -61,7 +61,7 @@ A private SSL/TLS key and a CSR tied to that key can be created in Mendix Cloud
 ### Generating a Certificate Request {#Generating}
 
 {{% alert color="info" %}}
-When you generate a certificate request at the application level, the resulting certificate is managed locally and applies only to that application. Therefore, Mendix recommends that you do not use a wildcard (`*`) in the domain for which you are requesting a certificate. See [Can You Create a `*.mycompany.com` Wildcard Certificate?](#wildcard), below, for more information.
+When you generate a certificate request at the application level, the resulting certificate is managed locally and applies only to that application. Therefore, Mendix recommends that you do not use a wildcard (`*`) in the domain for which you are requesting a certificate. See [Can You Create a `*.mycompany.com` Wildcard Certificate?](/developerportal/deploy/certificates/#wildcard), for more information.
 {{% /alert %}}
 
 To create a CSR and an RSA (Rivest–Shamir–Adleman) encryption key, follow these steps:
@@ -179,4 +179,4 @@ To edit an existing custom domain certificate, you need the following:
 
 * access to the certificate request that you created for the current certificate
 * [transport rights](/developerportal/deploy/node-permissions/#transport-rights) for all environments of the application
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md

@@ -86,25 +86,6 @@ Make sure you have configured a CNAME record for your custom domain with your do
 
 ## Frequently Asked Questions
 
-### Can You Create a `*.mycompany.com` Wildcard Certificate? {#wildcard}
-
-Yes. For application-level certificates, a wildcard certificate can only be used within the environments of a single app. This is because the private key is stored securely and cannot be accessed outside the app.
-
-To reuse a wildcard certificate across multiple apps or environments, Mendix Admins can create a central certificate in [Certificate Management](/control-center/certificate-management/). Central certificates can then be selected by Technical Contacts across different apps and environments.
-
-Technical Contacts can select the same wildcard certificate for different environments of the same app by using it with different subdomains. For example, `test.mycompany.com`, `accp.mycompany.com`, and `app.mycompany.com`.
-
-### How Do You Construct an Intermediate Certificate Chain Properly?
-
-Your certificate is signed by a certificate authority (CA) using the CA's intermediate certificate. The intermediate certificate is signed with the CA’s root certificate.
-
-To reach the root certificate, you must link your certificate through the intermediate certificate chain, usually just one intermediate certificate. Occasionally, a CA requires multiple intermediate certificates.
-
-* For application-level certificates, you provide the intermediate certificate chain when uploading the certificate at the application level
-* For central certificates, the chain is uploaded by the Mendix Admin
-
-You do not need to provide the root certificate, because every web browser has it in its trusted keystore.
-
 ### How Do You Get my SAML Metadata or CommunityCommons.GetApplicationUrl to Use the Custom URL? {#use-custom-url}
 
 For certain use cases, it is important for the Mendix runtime to know the public URL of your applications. This is most commonly needed when your app generates links back to itself.

content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md

@@ -31,7 +31,7 @@ The [PDF Document Generation](https://marketplace.mendix.com/link/component/2115
     {{% alert color="info" %}}We only support apps that allow bi-directional communication with the PDF Service in Mendix Cloud for all deployment types except for on-premises, and for the [Private PDF Document Generation Service](/appstore/services/private-document-generation-service/).{{% /alert %}}
 * The maximum file size is 25 MB per document. If your document exceeds this limit, the action will result in an exception. We recommend compressing high-resolution images to reduce their file size.
 * If your app is configured to [restrict access for incoming requests](/developerportal/deploy/access-restrictions/) using client certificates, our cloud service will not be able to reach your app, and the module will not work properly.
-* If your app uses a custom domain, you must configure a custom SSL/TLS domain certificate signed by a trusted public authority, including all intermediate certificates if applicable. Self-signed certificates will cause the service to fail. For more information, see [Obtaining a new signed certificate](/developerportal/deploy/custom-domains/#obtaining-a-new-signed-certificate).
+* If your app uses a custom domain, you must configure a custom SSL/TLS domain certificate signed by a trusted public authority, including all intermediate certificates if applicable. Self-signed certificates will cause the service to fail. For more information, see [Obtaining a new signed certificate](/developerportal/deploy/application-level-certificates/#obtaining-a-new-signed-certificate).
 * We use a fixed 30 second timeout for the page to finish loading and rendering. A timeout exception is thrown if the page content did not finish loading within 30 seconds.
 * Widgets or add-ons for your `index.html` file that perform long polling network requests are not supported. The document generation service waits until there are no more pending network requests.
 * Some widgets, such as [Charts](/appstore/widgets/charts/), might be rendered inconsistently in the generated PDF due to factors like animation.