website/integrations: random fixes (#17631)

* Change miniflux and espo-crm formatting

* Fixes capitalization, bolding and wording.

Author: dewi-tik

website/integrations/chat-communication-collaboration/espo-crm/index.md

@@ -38,9 +38,9 @@ To support the integration of EspoCRM with authentik, you need to create an appl
 - **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
 - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
-    - Set a `Strict` redirect URI to <kbd>https://<em>espocrm.company</em>/oauth-callback.php</kbd>.
+    - Set a `Strict` redirect URI to `https://espocrm.company/oauth-callback.php`.
     - Select any available signing key.
-    - Under **Advanced Protocol Settings**, set **Subject mode** to be `Based on the Users's username`.
+    - Under **Advanced protocol settings**, set **Subject mode** to be `Based on the Users's username`.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/chat-communication-collaboration/kimai/index.md

@@ -38,7 +38,7 @@ To support the integration of Kimai with authentik, you need to create an applic
     - Set the **Issuer** to `https://authentik.company`.
     - Set the **Service Provider Binding** to `Post`.
     - Set the **Audience** to `https://kimai.company/auth/saml`.
-    - Under **Advanced protocol settings**, select an available signing certificate.
+    - Under **Advanced protocol settings**, select an available **Signing certificate**.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/chat-communication-collaboration/mautic/index.md

@@ -73,8 +73,7 @@ Because Mautic requires a first name and last name attribute, create two [SAML p
         - Set the **ACS URL** to `https://mautic.company/s/saml/login_check`
         - Set the **Issuer** to `mautic.company`
         - Set the **Service Provider Binding** to `Post`
-        - Under **Advanced protocol settings** set the **Signing Certificate** to `authentik Self-signed Certificate` and check **Sign assertions** and **Sign responses**
-        - Under **Advanced protocol settings** add the newly created property mappings `SAML-FirstName-from-Name` and `SAML-LastName-from-Name` under **Property Mappings**. **Property Mappings**.
+        - Under **Advanced protocol settings**, select an available **Signing certificate**, check **Sign assertions** and **Sign responses**, and add the two **Property Mappings** you created in the previous section.
 3. Click **Submit** to save the new application and provider.
 4. Go to **Applications** > **Providers** and click on `mautic-provider`.
     - Under **Metadata** click on **Download** to save the file as `mautic-provider\_authentik_meta.xml`.

website/integrations/chat-communication-collaboration/nextcloud/index.mdx

@@ -122,7 +122,7 @@ To connect to an existing Nextcloud user, set the `nextcloud_user_id` attribute
         - Note the **Client ID** and **slug** values because they will be required later.
         - Set a `Strict` redirect URI to `https://nextcloud.company/apps/user_oidc/code`.
         - Select any available signing key.
-        - Under **Advanced Protocol Settings**:
+        - Under **Advanced protocol settings**:
             - _(optional)_ If you created the `Nextcloud Profile` scope mapping, add it to **Selected Scopes**.
             - **Subject Mode**: `Based on the User's UUID`
     - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
@@ -210,7 +210,7 @@ If you require [server side encryption](https://docs.nextcloud.com/server/latest
         - Set the **Issuer** to `https://authentik.company`.
         - Set the **Audience** to `https://nextcloud.company/apps/user_saml/saml/metadata`.
         - Set the **Service Provider Binding** to `Post`.
-        - Under **Advanced protocol settings**, set an available signing certificate.
+        - Under **Advanced protocol settings**, set an available **Signing certificate**.
     - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/chat-communication-collaboration/slack/index.md

@@ -51,7 +51,7 @@ To support the integration of Slack with authentik, you need to create an applic
     - Set the **ACS URL** to `https://company.slack.com/sso/saml`.
     - Set the **Issuer** to `https://slack.com`.
     - Set the **Service Provider Binding** to `Post`.
-    - Under **Advanced protocol settings**, add the two **Property Mappings** you created in the previous section, then select a **Signing Certificate**.
+    - Under **Advanced protocol settings**, select an available **Signing certificate** and add the two **Property Mappings** you created in the previous section.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/chat-communication-collaboration/zulip/index.md

@@ -36,7 +36,7 @@ To support the integration of Zulip with authentik, you need to create an applic
     - Set the **ACS URL** to `https://zulip.company/complete/saml/`.
     - Set the **Issuer** to `https://authentik.company`.
     - Set the **Service Provider Binding** to `Post`.
-    - Under **Advanced protocol settings**, select an available signing certificate.
+    - Under **Advanced protocol settings**, select an available **Signing certificate**.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/cloud-providers/aws/index.mdx

@@ -126,7 +126,7 @@ To support the integration of AWS with authentik using IAM Identity Center, you
 - **Configure the Provider**: provide a name (or accept the auto-provided name), and configure the following required settings:
     - Upload the metadata file from AWS (obtained in AWS Configuration steps)
     - Copy the **Issuer URL** to the **Audience** field
-    - Under **Advanced Protocol Settings**, set your **Signing Certificate**
+    - Under **Advanced protocol settings**, select an available **Signing certificate**.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.

website/integrations/cloud-providers/hashicorp-cloud/index.md

@@ -40,7 +40,7 @@ To support the integration of HashiCorp Cloud with authentik, you need to create
         - Set the **ACS URL** to the value of `SSO Sign-On URL` in the **HashiCorp Cloud preparation** section.
         - Set the **Issuer** and **Audience** to the value of `Entity ID` in the **HashiCorp Cloud preparation** section.
         - Set the **Service Provider Binding** to `Post`.
-        - Under **Advanced protocol settings**, select an available signing certificate.
+        - Under **Advanced protocol settings**, select an available **Signing certificate**.
 3. Click **Submit** to save the new application and provider.
 
 ## HashiCorp Cloud configuration

website/integrations/cloud-providers/ovhcloud/index.md

@@ -32,7 +32,7 @@ To support the integration of OVHcloud with authentik, you need to create an app
             - `https://www.ovhcloud.com/ca/auth/saml/acs` for CA region.
             - `https://us.ovhcloud.com/auth/` for US region.
         - Set the **Service Provider Binding** to `Post`.
-        - Under **Advanced protocol settings**, set an available signing certificate.
+        - Under **Advanced protocol settings**, set an available **Signing certificate**.
 
     - **Configure Bindings** _(optional)_: You can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 

website/integrations/development/engomo/index.mdx

@@ -48,7 +48,7 @@ To support the integration of Engomo with authentik, you need to create an appli
     - Set the **Client type** to `Public`.
     - Add two `Strict` redirect URIs and set them to `https://engomo.company/auth` and `com.engomo.engomo://callback/`.
     - Select any available signing key.
-    - Under **Advanced Protocol Settings**, add the scope you just created to the list of available scopes.
+    - Under **Advanced protocol settings**, add the scope you just created to the list of available scopes.
 - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
 
 3. Click **Submit** to save the new application and provider.