Fixing indents for lists and code blocks, and thus removing blockquot…

…es in the resulting pages

docs/manual/docs/administrator-guide/configuring-the-catalog/index.md

@@ -1,9 +1,9 @@
 # Configuring the catalog
 
--   [system-configuration](system-configuration.md)
--   [user-interface-configuration](user-interface-configuration.md)
--   [css-configuration](css-configuration.md)
--   [csw-configuration](csw-configuration.md)
--   [portal-configuration](portal-configuration.md)
--   [inspire-configuration](inspire-configuration.md)
--   [map-server-configuration](map-server-configuration.md)
+-   [System configuration](system-configuration.md)
+-   [User Interface Configuration](user-interface-configuration.md)
+-   [Configuring CSS & Style](css-configuration.md)
+-   [Configuring CSW](csw-configuration.md)
+-   [Portal Configuration](portal-configuration.md)
+-   [Configuring for the INSPIRE Directive](inspire-configuration.md)
+-   [Map servers configuration for geopublication](map-server-configuration.md)

docs/manual/docs/administrator-guide/configuring-the-catalog/inspire-configuration.md

@@ -2,7 +2,7 @@
 
 ## Enabling INSPIRE
 
-From the :**Admin console \--> Settings** user can configure INSPIRE directive support.
+From the **Admin console -> Settings** user can configure INSPIRE directive support.
 
 When enabled, the INSPIRE support activate the following:
 

docs/manual/docs/administrator-guide/configuring-the-catalog/portal-configuration.md

@@ -6,9 +6,9 @@ Portals can be configured under the `sources` section in `admin console` > `sett
 
 There are 3 types of sources:
 
-> -   the main catalogue,
-> -   sub-portal, which can be a subset of the main catalogue
-> -   harvesters.
+-   the main catalogue,
+-   sub-portal, which can be a subset of the main catalogue
+-   harvesters.
 
 ![](img/portal-types.png)
 

docs/manual/docs/administrator-guide/managing-metadata-standards/standards.md

@@ -24,27 +24,27 @@ To add a metadata schema to the catalog, a rebuild of the sources is required. I
 -   Verify and if compatible update the version of GeoNetwork (parent) referenced from the pom.xml file in the schema plugin.
 -   Add a reference in /schemas/pom.xml to the newly added schema
 
-``` xml
-<module>{myschema}</module>
-```
+    ``` xml
+    <module>{myschema}</module>
+    ```
 
 -   Add references to the newly added schema in /web/pom.xml
 
-``` xml
-<dependency>
-  <groupId>${project.groupId}</groupId>
-  <artifactId>{myschema}</artifactId>
-  <version>${project.version}</version>
-</dependency>
-```
+    ``` xml
+    <dependency>
+      <groupId>${project.groupId}</groupId>
+      <artifactId>{myschema}</artifactId>
+      <version>${project.version}</version>
+    </dependency>
+    ```
 
 -   and
 
-``` xml
-<resource>
-  <directory>${project.basedir}/../schemas/{myschema}/src/main/plugin</directory>
-  <targetPath>${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins</targetPath>
-</resource>
-```
+    ``` xml
+    <resource>
+      <directory>${project.basedir}/../schemas/{myschema}/src/main/plugin</directory>
+      <targetPath>${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins</targetPath>
+    </resource>
+    ```
 
 Then Build and deploy your instance of GeoNetwork.

docs/manual/docs/administrator-guide/managing-users-and-groups/authentication-mode.md

@@ -510,7 +510,7 @@ The `et` you configured on your OpenID server.
 
 **OPENIDCONNECT_SERVERMETADATA_CONFIG_URL**
 
-URL to the external OIDC server's JSON metadata document. This is typically at [/.well-known/openid-configuration]{.title-ref} on the IDP server.
+URL to the external OIDC server's JSON metadata document. This is typically at [/.well-known/openid-configuration] on the IDP server.
 
 !!! note
 
@@ -533,7 +533,7 @@ Where, in the ID Token, are the users roles/groups stored (i.e. "groups", "roles
 
 This provides simple role conversion from the OpenID server to Geonetwork roles.
 
-ie. ["GeonetworkAdmin=Administrator,GeonetworkEditor=Editor"]{.title-ref}
+ie. ["GeonetworkAdmin=Administrator,GeonetworkEditor=Editor"]
 
 This will convert "GeonetworkAdmin" (from the OpenID Server) to the Geonetwork "Administrator" role.
 
@@ -772,13 +772,13 @@ Install keycloak from its instructions or use this example setup in docker <http
 
 Keycloak details are defined via environment variables
 
-> ``` text
+``` text
 > KEYCLOAK_AUTH_SERVER_URL={keycloak url}
 > KEYCLOAK_REALM={realm name}
 > KEYCLOAK_RESOURCE={client name}
 > KEYCLOAK_SECRET={client secret}
 > KEYCLOAK_DISABLE_TRUST_MANAGER={true|false}
-> ```
+```
 
 You can setup more advance keycloak settings by editing the file `WEB-INF/config-security/keycloak.json`{.interpreted-text role="file"}
 

docs/manual/docs/contributing/style-guide.md

@@ -4,7 +4,7 @@ This is a work-in-progress style guide to help creating consistent documentation
 
 ## Preferred Terminology
 
-> -   Catalog Home Page
-> -   GeoNetwork (check capitalisation, or preferably use the `GeoNetwork` variable)
-> -   Metadata Catalog
-> -   Sub-Portal
+-   Catalog Home Page
+-   GeoNetwork (check capitalisation, or preferably use the `GeoNetwork` variable)
+-   Metadata Catalog
+-   Sub-Portal

docs/manual/docs/customizing-application/characterset.md

@@ -1,15 +1,17 @@
 # Characterset
 
-By default the character set of GeoNetwork is UTF-8. This works well for many locales in the world and is compatible with ASCII that is typically used in US and Canada. However, if UTF-8 is not a compatible characterset in your environment you can change the default.
+By default the character set of GeoNetwork is `UTF-8`. This works well for many locales in the world and is compatible with ASCII that is typically used in US and Canada. However, if `UTF-8` is not a compatible characterset in your environment you can change the default.
 
 To change it within GeoNetwork simply start the application with the system property geonetwork.file.encoding set to the desired character set name.
 
 For example if you are running Tomcat you can set
 
+```
 JAVA_OPTS="-Dgeonetwork.file.encoding=UTF-16"
+```
 
-to the startup script and the default codec in GeoNetwork will be UTF-16.
+to the startup script and the default codec in GeoNetwork will be `UTF-16`.
 
 It is also recommended to set the file.encoding parameter to the same codec as this dictates to the default encoding used in Java and the Web Server may reference at times use the default codec.
 
-Finally, by default the URL parameters are typically interpreted as ASCII characters which can be a problem when searching for metadata that are not in the english language. Each Web Server will have a method for configuring the encoding used when reading the parameters. For example, in Tomcat the encoding/charset configuration is in the server.xml Connector element.
+Finally, by default the URL parameters are typically interpreted as ASCII characters which can be a problem when searching for metadata that are not in the english language. Each Web Server will have a method for configuring the encoding used when reading the parameters. For example, in Tomcat the encoding/charset configuration is in the `server.xml` Connector element.

docs/manual/docs/customizing-application/index.md

@@ -1,10 +1,10 @@
 # Customizing guide
 
--   [Search Ui Index](search-ui/index.md)
+-   [Search UI Index](search-ui/index.md)
 -   [Creating Custom View](creating-custom-view.md)
--   [Editor Ui Creating Custom Editor](editor-ui/creating-custom-editor.md)
--   [Editor Ui Custom Editor Examples](editor-ui/custom-editor-examples.md)
--   [Editor Ui Tutorial](editor-ui/tutorial.md)
+-   [Editor UI Creating Custom Editor](editor-ui/creating-custom-editor.md)
+-   [Editor UI Custom Editor Examples](editor-ui/custom-editor-examples.md)
+-   [Editor UI Tutorial](editor-ui/tutorial.md)
 -   [Changing Layout](changing-layout.md)
 -   [Configuring Search Fields](configuring-search-fields.md)
 -   [Configuring Faceted Search](configuring-faceted-search.md)