[ENDOC-684] Remove break lines in favor of blank lines to avoid error…

vuepress/docs/next/tutorials/devops/backing-restoring-keycloak.md

@@ -24,13 +24,7 @@ mkdir -p /tmp/export
 
 4. Run the following script to retrieve the data for the Entando realm and save it to a JSON file in the `export` directory. A new Keycloak server will run on a different port (offset=200) to avoid conflicts with the original Entando Keycloak instance.
 ```
-/opt/jboss/keycloak/bin/standalone.sh
--Djboss.socket.binding.port-offset=200
--Dkeycloak.migration.action=export 
--Dkeycloak.migration.provider=singleFile 
--Dkeycloak.migration.realmName=entando
--Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES 
--Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
+/opt/jboss/keycloak/bin/standalone.sh -Djboss.socket.binding.port-offset=200 -Dkeycloak.migration.action=export  -Dkeycloak.migration.provider=singleFile  -Dkeycloak.migration.realmName=entando -Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES -Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
 ```
 5. If there are no errors, press Ctrl+C to stop the process.
 6. Type `exit` to close the bash shell in the pod.
@@ -51,4 +45,4 @@ kubectl cp YOUR-KEYCLOAK-POD-NAME:/tmp/export/ keycloak-backup
 
 ::: tip Note
 If you are using a different environment, with a different hostname, you should import only users or set the flag for `If a resource exists` to `Skip`.
-:::
+:::

vuepress/docs/v6.3.2/tutorials/devops/backing-restoring-keycloak.md

@@ -24,13 +24,7 @@ mkdir -p /tmp/export
 
 4. Run the following script to retrieve the data for the entando realm and save it to a JSON file in the `export` directory. A new Keycloak server will run on a different port (offset=200) to avoid conflicts with the original Entando Keycloak instance.
 ```
-/opt/jboss/keycloak/bin/standalone.sh
--Djboss.socket.binding.port-offset=200
--Dkeycloak.migration.action=export 
--Dkeycloak.migration.provider=singleFile 
--Dkeycloak.migration.realmName=entando
--Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES 
--Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
+/opt/jboss/keycloak/bin/standalone.sh -Djboss.socket.binding.port-offset=200 -Dkeycloak.migration.action=export  -Dkeycloak.migration.provider=singleFile  -Dkeycloak.migration.realmName=entando -Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES -Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
 ```
 5. If there are no errors, press Ctrl+C to stop the process.
 6. Type `exit` to close the bash shell in the pod.
@@ -51,4 +45,4 @@ kubectl cp [keycloak-pod-name]:/tmp/export/ keycloak-backup
 
 ::: tip Note
 If you are using a different environment, with a different hostname, you should import only users or set the flag for `If a resource exists` to `Skip`.
-:::
+:::

vuepress/docs/v7.0/tutorials/devops/backing-restoring-keycloak.md

@@ -24,13 +24,7 @@ mkdir -p /tmp/export
 
 4. Run the following script to retrieve the data for the Entando realm and save it to a JSON file in the `export` directory. A new Keycloak server will run on a different port (offset=200) to avoid conflicts with the original Entando Keycloak instance.
 ```
-/opt/jboss/keycloak/bin/standalone.sh
--Djboss.socket.binding.port-offset=200
--Dkeycloak.migration.action=export 
--Dkeycloak.migration.provider=singleFile 
--Dkeycloak.migration.realmName=entando
--Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES 
--Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
+/opt/jboss/keycloak/bin/standalone.sh -Djboss.socket.binding.port-offset=200 -Dkeycloak.migration.action=export  -Dkeycloak.migration.provider=singleFile  -Dkeycloak.migration.realmName=entando -Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES -Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
 ```
 5. If there are no errors, press Ctrl+C to stop the process.
 6. Type `exit` to close the bash shell in the pod.
@@ -51,4 +45,4 @@ kubectl cp YOUR-KEYCLOAK-POD-NAME:/tmp/export/ keycloak-backup
 
 ::: tip Note
 If you are using a different environment, with a different hostname, you should import only users or set the flag for `If a resource exists` to `Skip`.
-:::
+:::

vuepress/docs/v7.1/tutorials/devops/backing-restoring-keycloak.md

@@ -24,13 +24,7 @@ mkdir -p /tmp/export
 
 4. Run the following script to retrieve the data for the Entando realm and save it to a JSON file in the `export` directory. A new Keycloak server will run on a different port (offset=200) to avoid conflicts with the original Entando Keycloak instance.
 ```
-/opt/jboss/keycloak/bin/standalone.sh
--Djboss.socket.binding.port-offset=200
--Dkeycloak.migration.action=export 
--Dkeycloak.migration.provider=singleFile 
--Dkeycloak.migration.realmName=entando
--Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES 
--Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
+/opt/jboss/keycloak/bin/standalone.sh -Djboss.socket.binding.port-offset=200 -Dkeycloak.migration.action=export  -Dkeycloak.migration.provider=singleFile  -Dkeycloak.migration.realmName=entando -Dkeycloak.migration.usersExportStrategy=DIFFERENT_FILES -Dkeycloak.migration.file=/tmp/export/entando-prod-realm.json
 ```
 5. If there are no errors, press Ctrl+C to stop the process.
 6. Type `exit` to close the bash shell in the pod.
@@ -51,4 +45,4 @@ kubectl cp YOUR-KEYCLOAK-POD-NAME:/tmp/export/ keycloak-backup
 
 ::: tip Note
 If you are using a different environment, with a different hostname, you should import only users or set the flag for `If a resource exists` to `Skip`.
-:::
+:::