anchor.diff:  kubectl apply -f example-realm-import.yaml
   ----
   
  -And you can check the progress of the Import by running:
  +You can check the status of the running import by using the following command:
   
   [source,bash]
   ----
   kubectl get keycloakrealmimports/my-realm-kc -o go-template='{{range .status.conditions}}CONDITION: {{.type}}{{"\n"}}  STATUS: {{.status}}{{"\n"}}  MESSAGE: {{.message}}{{"\n"}}{{end}}'
   ----
   
  -When the import successfully completed the output will look like follow:
  +When the import has successfully completed, the output will look like the example below:
   
   [source,bash]
   ----
  
positive.code: 
  .Note:
  [NOTE]
  The Realm Import CR only supports creation of new realms and doesn't updates or delete those. +
  Changes to the realm performed directly on Keycloak are not synched back in the CR.
  
  === Writing Realm Import CR
  
  A Realm Import Custom Resource(CR) looks like follows:
  
  [source,yaml]
  ----
  
negative.code:     ...
  ----
  
  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 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
  