fix: oss common admonition

Author: vinckr

docs/_common/need-selfhosted-support.mdx

@@ -0,0 +1,6 @@
+:::info Professional support?
+
+Ory offers support for self-hosted Ory software through the Ory Enterprise License (OEL). Read more about the OEL
+[here](https://www.ory.sh/docs/self-hosted/oel).
+
+:::

docs/ecosystem/changelog.mdx

@@ -6,7 +6,7 @@ title: Changelog and roadmap
 ## Ory Changelog
 
 ```mdx-code-block
-import Help from '@site/docs/_common/need-help.mdx'
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
 
 <Help/>
 ```

docs/hydra/self-hosted/quickstart.mdx

@@ -5,6 +5,12 @@ title: Quickstart
 
 # Ory Hydra OAuth2 Server Quickstart
 
+```mdx-code-block
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
+
+<Help/>
+```
+
 In this quickstart, you will set up Ory Hydra OAuth2 & OpenID Connect Server and an exemplary User Login & Consent App using
 Docker Compose. You need to have the latest [Docker](https://www.docker.com) and [Docker Compose](https://docs.docker.com/compose)
 version and Git installed, as well as [`jq`](https://stedolan.github.io/jq/download/).

docs/keto/quickstart.mdx

@@ -2,20 +2,22 @@
 title: "Quickstart: Cat Videos Example"
 ---
 
+```mdx-code-block
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
+
+<Help/>
+```
+
 This example describes a video sharing service. The individual videos are organized in directories. Every directory has an owner
 and every video has the same owner as it's parent directory. The owner has elevated privileges about the video files that aren't
 modeled individually in Ory Keto. The only other privilege modeled in this example is "view access." Every owner has view access
 to their objects, and this privilege can be granted to other users as well. The video sharing application interprets the special
 `*` user ID as any user, including anonymous users. Note that Ory Keto doesn't interpret this subject any differently from other
 subjects. It also doesn't know anything about directory structures or induced ownership.
 
-:::info Terminology
-
 The "Keto client" is the application interacting with Keto. In this case we refer to the video sharing service backend as the Keto
 client.
 
-:::
-
 ## Starting the example
 
 First, [install Keto](./install.mdx).

docs/kratos/quickstart.mdx

@@ -5,6 +5,12 @@ title: Quickstart
 
 # Ory Kratos Identity Server Quickstart
 
+```mdx-code-block
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
+
+<Help/>
+```
+
 import Mermaid from "@site/src/theme/Mermaid"
 import CodeFromRemote from "@site/src/theme/CodeFromRemote"
 

docs/oathkeeper/configure-deploy.mdx

@@ -5,8 +5,8 @@ title: Configure and deploy
 
 The Ory Oathkeeper HTTP serve process `oathkeeper serve` opens two ports exposing the
 
-- [reverse proxy](index.md#reverse-proxy)
-- REST API which serves the [Access Control Decision API](index.md#access-control-decision-api) as well as other API endpoints
+- [reverse proxy](index.mdx#reverse-proxy)
+- REST API which serves the [Access Control Decision API](index.mdx#access-control-decision-api) as well as other API endpoints
   such as health checks, JSON Web Key Sets, and a list of available rules.
 
 For this guide we're using Docker. Ory Oathkeeper however can be [installed in a variety of ways](install.mdx).

docs/oathkeeper/guides/traefik-proxy-integration.md

@@ -5,7 +5,7 @@ title: Traefik proxy integration
 
 [Traefik](https://doc.traefik.io/traefik/) is modern HTTP proxy and load balancer for microservices, oathkeeper can be integrated
 with via the [ForwardAuth Middleware](https://doc.traefik.io/traefik/middlewares/http/forwardauth/) by making use of the available
-[Access Control Decision API](../index.md#access-control-decision-api).
+[Access Control Decision API](../index.mdx#access-control-decision-api).
 
 To achieve this,
 

docs/oathkeeper/index.md renamed to docs/oathkeeper/index.mdx

@@ -3,6 +3,12 @@ id: index
 title: Introduction to Ory Oathkeeper Zero Trust Proxy
 ---
 
+```mdx-code-block
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
+
+<Help/>
+```
+
 Ory Oathkeeper authorizes incoming HTTP requests. It can be the Policy Enforcement Point in your cloud architecture, i.e. a
 reverse proxy in front of your upstream API or web server that rejects unauthorized requests and forwards authorized ones to your
 server. If you want to use another API Gateway (Kong, Nginx, Envoy, AWS API Gateway, ...), Oathkeeper can also plug into that and

docs/polis/quickstart.mdx

@@ -5,6 +5,12 @@ title: Quickstart
 
 # Get started with SAML Single Sign-On authentication
 
+```mdx-code-block
+import Help from '@site/docs/_common/need-selfhosted-support.mdx'
+
+<Help/>
+```
+
 Ory Polis can be used with any web application to integrate Single Sign-On (SSO) authentication.
 
 There are two ways to integrate Ory Polis with an application. Depending on your use case, you can choose either one of them.