anchor.diff:      ...
   ----
   
  -This CR should be created in the same namespace as the Keycloak Deployment CR defined in the field `keycloakCRName`.
  -The `realm` field accepts a full https://www.keycloak.org/docs-api/{version}/rest-api/index.html#_realmrepresentation[RealmRepresentation].
  +This CR should be created in the same namespace as the Keycloak Deployment CR, defined in the field `keycloakCRName`.
  +The `realm` field accepts a full https://www.keycloak.org/docs-api/{majorMinorVersion}/rest-api/index.html#_realmrepresentation[RealmRepresentation].
   
  -The suggested way to obtain a `RealmRepresentation` is leveraging the export functionality <@links.server id="importExport"/>
  +The recommended way to obtain a `RealmRepresentation` is leveraging the export functionality <@links.server id="importExport"/>
   
   * export the Realm to a single file
   * convert the json to yaml
  
positive.code: <@tmpl.guide
  title="Keycloak Realm Import"
  priority=30
  summary="How to perform an automated Keyacloak Realm Import">
  
  == Keycloak Realm Import
  
  The Keycloak Operator ships with the feature of automatically perform a realm import for the Keycloak Deployment.
  
  .Note:
  [NOTE]
  
negative.code: 
  .Note:
  [NOTE]
  The Realm Import CR only supports creation of new realms and doesn't update or delete those. +
  Changes to the realm performed directly on Keycloak are not synced back in the CR.
  
  === Writing Realm Import CR
  
  A Realm Import Custom Resource (CR) looks like follows:
  
  [source,yaml]
  ----
  