Fix images and markup in the Enterprise docs

src/content/docs/aws/pro/enterprise-image.md

@@ -27,6 +27,7 @@ This offline functionality is enabled by:
 - After the image is pushed to the customer-specific ECR repository, the customer can pull and push it to their internal Docker registry.
 - Developers within the customer’s network can then pull the image from this registry.
 - To use the image from the command line interface (CLI), set the `IMAGE_NAME` configuration to the name of the Enterprise image, typically using the command:
-    {{< command >}}
+
+    ```bash
     $ IMAGE_NAME=localstack-enterprise localstack start
-    {{< / command >}}
+    ```

src/content/docs/aws/pro/enterprise-support.md

@@ -28,9 +28,7 @@ Currently, the **customer portal** is only **available to Enterprise customers**
 
 You can find the customer portal here: [https://support.localstack.cloud/portal](https://support.localstack.cloud/portal)
 
-<p>
-{{< img src="customer-portal.png" alt="Customer portal for enterprise support" class="img-fluid shadow rounded" width="800px" >}}
-</p>
+![Customer portal for enterprise support](/images/aws/customer-portal.png)
 
 ## Signing up for Enterprise Support
 
@@ -45,9 +43,7 @@ Once you do so, you will be able to log in and start using the customer portal t
 You can open a new ticket with LocalStack support by going to the **Create a Support Ticket** link.
 You will be redirected to a form where you will have to provide certain information to file a new support ticket.
 
-<p>
-{{< img src="file-a-support-ticket.png" alt="Filing a support ticket" class="img-fluid shadow rounded" width="800px" >}}
-</p>
+![Filing a support ticket](/images/aws/file-a-support-ticket.png)
 
 The form consists of two parts.
 One is basic information, which is mandatory to fill out, and additional information, which adds more context to your issue but is not mandatory.

src/content/docs/aws/pro/k8s-operator.md

@@ -15,10 +15,10 @@ The operator is designed to simplify the deployment and management of LocalStack
 
 To install the K8s operator, run the following commands:
 
-{{< command >}}
-$ kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-operator/v0.2.0/release/crds.yaml
-$ kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-operator/v0.2.0/release/controller.yaml
-{{< / command >}}
+```bash
+kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-operator/v0.2.0/release/crds.yaml
+kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-operator/v0.2.0/release/controller.yaml
+```
 
 You can then deploy a LocalStack instance by storing the following file content as `localstack.yml` and applying it against the cluster via `kubectl apply -f localstack.yml`.
 

src/content/docs/aws/pro/sso.md

@@ -11,7 +11,7 @@ Custom Single-Sign On (SSO) Identity providers, can be enabled to facilitate the
 In order to configure SSO access, first sign in to the LocalStack Web application under [app.localstack.cloud](https://app.localstack.cloud/).
 In your profile settings, navigate to the Single Sign-on tab which will list existing SSO Identity Providers (if any exist).
 
-<img src="localstack-setting-sso.png" width="800px" alt="Adding SSO Identity providers in LocalStack Settings">
+![Adding SSO Identity providers in LocalStack Settings](/images/aws/localstack-setting-sso.png)
 
 Next, click the button to create a new identity provider (IdP), where you can choose between the two leading industry standards:
 
@@ -26,7 +26,7 @@ In the form illustrated below, you can then enter the main information for the n
 - Client ID, Client Secret, Attributes request method, OIDC issues, Authorize scopes, and more.
   - You should be able to find these attributes in your OIDC IdP configuration.
 
-<img src="oidc-sso.png" width="600px" alt="Configuring SSO using OpenID Connect (OIDC)">
+![Configuring SSO using OpenID Connect (OIDC)](/images/aws/oidc-sso.png)
 
 ## Configuring SSO using SAML
 
@@ -35,7 +35,7 @@ The SAML metadata file can be specified either via URL or via a file upload.
 
 Select **Enable IdP sign out flow** if you want your users to be logged out from our app and your SAML IdP when they log out from your our Web Application.
 
-<img src="saml-sso.png" width="600px" alt="Configuring SSO using SAML">
+![Configuring SSO using SAML](/images/aws/saml-sso.png)
 
 ## Attribute mapping
 
@@ -49,7 +49,7 @@ The following user attribute mappings can currently be configured:
 
 The Email should be configured to ensure correct functionality.
 
-<img src="attribute-mapping.png" width="600px" alt="Attribute Mapping">
+![Attribute Mapping](/images/aws/attribute-mapping.png)
 
 ## Callback URL, Sign Up Portal URL and Identifier (Entity Id)
 
@@ -60,7 +60,7 @@ After configuring the base details for your Identity Provider (IdP), the followi
 - **Sign Up Portal URL**: This is the URL that can be shared with your users to start the SSO signup flow for the LocalStack Web Application.
   The format of this endpoint is `https://app.localstack.cloud/auth/sso/<organizationId>/<ssoName>`
 
-<img src="additional-information-page.png" width="600px" alt="Callback URL, Sign Up Portal URL, and Identifier (Entity Id)">
+![Callback URL, Sign Up Portal URL, and Identifier (Entity Id)](/images/aws/additional-information-page.png)
 
 ## User Roles and Permissions
 
@@ -70,4 +70,5 @@ For each new member that joins your org, you can specify user roles and permissi
 - **Default User Permissions**: Use this to define which permissions should be assigned to users of your organization signing up via SSO.
   - Tip: In order to enable self-serve licences (i.e., allowing your users to allocate themselves their own license), make sure to select the **Allow member to issue a license for themselves (or a legacy API key)** permission.
 
-<img src="roles-permissions.png" width="600px" alt="User Roles and Permissions">
+
+![User Roles and Permissions](/images/aws/roles-permissions.png)