docs: small fixes across docs (#11687)

# Which Problems Are Solved

This PR fixes a couple of minor issues in the docs:
- Duplicated sentences
- Obsolete names
- Wrong header hierarchy 

# How the Problems Are Solved

Solved by rewriting/fixing the mdx files.

# Additional Changes

none

# Additional Context

none
This commit is contained in:
Vitor Bari Buccianti
2026-02-27 11:44:35 +01:00
committed by GitHub
parent 7a72e7207e
commit a3d0df1f4c
6 changed files with 11 additions and 11 deletions
@@ -29,7 +29,7 @@ Follow this guide to configure your ZITADEL instance for this scenario.
You will use the instance default settings for the login for the organization **CIAM**.
When opening `login.mycompany.com` then the login policy of the instance will be applied.
This means that you have to set up the [Login and Access](/guides/manage/console/default-settings#login-behavior-and-access) Policy and [Identity Providers](/guides/manage/console/default-settings#identity-providers) for the **CIAM** users on the instance itself.
This means that you have to set up the [Login and Access](/guides/manage/console/default-settings#login-behavior-and-security) Policy and [Identity Providers](/guides/manage/console/default-settings#identity-providers) for the **CIAM** users on the instance itself.
<Callout>
You can also configure these settings on the default organization (see below) and send the scope `urn:zitadel:iam:org:id:{id}` with every [auth request](https://zitadel.com/playgrounds/oidc).
@@ -44,7 +44,7 @@ The default organization will hold all unmatched users, ie. all users that are n
### Enable Domain Discovery
In the [Login Behavior and Security Settings](/guides/manage/console/default-settings#login-behavior-and-access) enable "Domain discovery allowed"
In the [Login Behavior and Security Settings](/guides/manage/console/default-settings#login-behavior-and-security) enable "Domain discovery allowed"
### Configure login with email