Fix: Updated directory placeholders to use consistent format

Author: mmafrar

en/asgardeo/docs/get-started/try-samples/qsg-oidc-webapp-java-ee.md

@@ -82,9 +82,9 @@ Click the button below to download the sample. You can also choose to view the s
 
 Follow the steps given below to configure the sample app.
 
-1. Move the  **war** file that you downloaded to the `{TOMCAT_HOME}/webapps` folder where `{TOMCAT_HOME}` is the home directory of your Tomcat server.
+1. Move the  **war** file that you downloaded to the `<TOMCAT_HOME>/webapps` folder where `<TOMCAT_HOME>` is the home directory of your Tomcat server.
 
-2. Open a terminal, navigate to the `{TOMCAT_HOME}/bin` folder, and start the Tomcat server using the following command:
+2. Open a terminal, navigate to the `<TOMCAT_HOME>/bin` folder, and start the Tomcat server using the following command:
 
     ```bash 
     sh catalina.sh start
@@ -94,7 +94,7 @@ Follow the steps given below to configure the sample app.
         This will extract the contents of the **war** file. </br>
         If your Tomcat server is set to auto-deploy applications, you can skip this step.
 
-3. Go to the `{TOMCAT_HOME}/webapps/oidc-sample-app/WEB-INF/classes` folder and open the `oidc-sample-app.properties` file in a text editor.
+3. Go to the `<TOMCAT_HOME>/webapps/oidc-sample-app/WEB-INF/classes` folder and open the `oidc-sample-app.properties` file in a text editor.
 4. Update the following in the `oidc-sample-app.properties` file:
 
     ``` json
@@ -188,7 +188,7 @@ Follow the steps given below to configure the sample app.
     </tr>
     </table>
 
-5. On your terminal, navigate to the `{TOMCAT_HOME}/bin` folder and run the following commands to restart the Tomcat server for the configurations to take effect:
+5. On your terminal, navigate to the `<TOMCAT_HOME>/bin` folder and run the following commands to restart the Tomcat server for the configurations to take effect:
 
     ```bash 
     sh catalina.sh stop

en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md

@@ -91,9 +91,9 @@ Click the button below to download the sample. You can also choose to view the s
 
 Follow the steps given below to configure the sample app.
 
-1. Move the  **war** file that you downloaded to the `{TOMCAT_HOME}/webapps` folder where `{TOMCAT_HOME}` is the root of your Tomcat server.
+1. Move the  **war** file that you downloaded to the `<TOMCAT_HOME>/webapps` folder where `<TOMCAT_HOME>` is the root of your Tomcat server.
 
-2. Open a terminal, navigate to the `{TOMCAT_HOME}/bin` folder, and start the Tomcat server using the following command:
+2. Open a terminal, navigate to the `<TOMCAT_HOME>/bin` folder, and start the Tomcat server using the following command:
 
     !!! note
         This will extract the contents of the **war** file. </br>
@@ -103,7 +103,7 @@ Follow the steps given below to configure the sample app.
     sh catalina.sh start
     ```
 
-3. Go to the `{TOMCAT_HOME}/webapps/sample-app/WEB-INF/classes` folder and open the `sample-app.properties` file in a text editor.
+3. Go to the `<TOMCAT_HOME>/webapps/sample-app/WEB-INF/classes` folder and open the `sample-app.properties` file in a text editor.
 
 4. Update the following in the `sample-app.properties` file:
 
@@ -286,7 +286,7 @@ Follow the steps given below to configure the sample app.
           </tbody>
         </table>
 
-5. In the `{TOMCAT_HOME}/bin` folder, run the following commands to restart the Tomcat server for the configurations to take effect:
+5. In the `<TOMCAT_HOME>/bin` folder, run the following commands to restart the Tomcat server for the configurations to take effect:
 
     ```bash
     sh catalina.sh stop

en/identity-server/5.10.0/docs/administer/configuring-tls-termination.md

@@ -18,7 +18,7 @@ Termination](https://www.nginx.com/resources/admin-guide/nginx-ssl-termination/)
 ### Step 2: Enabling RemoteIpValve for Carbon servers
 
 You can enable Tomcat's RemoteIpValve for your Carbon server by simply
-adding the configuration to `<IS-HOME>/repository/conf/deployment.toml` See the [Tomcat
+adding the configuration to `<IS_HOME>/repository/conf/deployment.toml` See the [Tomcat
 documentation](https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/valves/RemoteIpValve.html)
 for more information about `         RemoteIpValve        ` .
 

en/identity-server/5.10.0/docs/administer/enabling-mutual-ssl.md

@@ -15,9 +15,9 @@ they are `          jks         ` files. Let's take a look at where the
 JKS files are saved:
 
 -   WSO2 Identity Server certificates are stored in the
-    `           <IS-HOME>/repository/resources/security/wso2carbon.jks          ` file.
+    `           <IS_HOME>/repository/resources/security/wso2carbon.jks          ` file.
 -   Server side certificates are stored in the
-    `           <IS-HOME>/repository/resources/security/clienttruststore.jks          ` file.
+    `           <IS_HOME>/repository/resources/security/clienttruststore.jks          ` file.
 
 These certificates are signed and issued by a certificate authority that
 allows both the client and server to communicate freely. Now let's look

en/identity-server/5.10.0/docs/administer/mitigating-cross-site-request-forgery-attacks.md

@@ -130,7 +130,7 @@ Follow the steps below to secure web applications.
 3.  Create a CSRF configuration properties file (e.g.
     `          abc.properties         ` ) within your application, and
     copy the content in the
-    `          <CARBON_HOME>repository/conf/security/         `
+    `          <CARBON_HOME>/repository/conf/security/         `
     `          Owasp.CsrfGuard.Carbon.properties         ` file to it.
 4.  Use the `           org.owasp.csrfguard.unprotected.          `
     prefix in the configuration property keys, for the relevant patterns
@@ -212,7 +212,7 @@ Follow the steps below to secure Jaggery applications.
 3.  Create a CSRF configuration properties file (e.g.
     `          abc.properties         ` ) within your application, and
     copy the content in the
-    `          <CARBON_HOME>repository/conf/security/         `
+    `          <CARBON_HOME>/repository/conf/security/         `
     `          Owasp.CsrfGuard.Carbon.properties         ` file to it.
 4.  Use the `           org.owasp.csrfguard.unprotected.          `
     prefix in the configuration property keys, for the relevant patterns

en/identity-server/5.10.0/docs/administer/mutual-tls-with-client-id-and-secret-using-oidc.md

@@ -23,7 +23,7 @@ In order to consume the request, follow the steps given below.
     token request and the service provider. This validation needs to be skipped.
 
     For achieving both above requirements add the following configuration to the 
-    `<IS-HOME>/repository/conf/deployment.toml`
+    `<IS_HOME>/repository/conf/deployment.toml`
 
     ``` toml
      [[event_listener]]

en/identity-server/5.10.0/docs/administer/registry-related-tables.md

@@ -223,7 +223,7 @@ data section of a resource). Apart from that, versioning can be done per
 each change made for a resource which can be an extremely expensive
 operation at runtime (especially if there are many resources that
 change). By setting the `\<versionResourcesOnChange\>` parameter in
-`<IS_HOME\>/repository/conf/registry.xml` to `true/false`, you can
+`<IS_HOME>/repository/conf/registry.xml` to `true/false`, you can
 enable/disable versioning resources on change. If it is enabled, upon
 modification to a resource, a new version will be created from the
 resource and also a new record is added to this table. Following are the

en/identity-server/5.10.0/docs/develop/customizing-error-pages.md

@@ -13,7 +13,7 @@ messages in Apache Tomcat.
 The pages that should be displayed on a
 certain throwable exception, error or an HTTP status code are specified
 in the
-`          <IS_HOME>repository/conf/tomcat/carbon/WEB-INF/web.xml ` file. You can customize those error pages as preferred. For example,
+`          <IS_HOME>/repository/conf/tomcat/carbon/WEB-INF/web.xml ` file. You can customize those error pages as preferred. For example,
 if you try to access a resource that is not available in the Carbon
 server (e.g., https://localhost:9443/abc), you will see the "Error 404 - Not Found"
 page.

en/identity-server/5.10.0/docs/develop/customizing-the-authentication-endpoint.md

@@ -89,7 +89,7 @@ Do the following configurations to enable this feature.
         directory.
 
 2.  Open the
-    `           <IS-HOME>/repository/conf/deployment.toml          `
+    `           <IS_HOME>/repository/conf/deployment.toml          `
     file and add the following parameter to enable the Mutual SSL Authenticator.
 
     ```toml
@@ -109,7 +109,7 @@ Do the following configurations to enable this feature.
 
 4.  Add the following configuration into the
                         `
-    `<IS-HOME>/repository/conf/deployment.toml`.
+    `<IS_HOME>/repository/conf/deployment.toml`.
 
     ```toml
     [tenant]

en/identity-server/5.10.0/docs/develop/customizing-the-sso-redirection-page.md

@@ -1,6 +1,6 @@
 # Re-branding the SSO Redirection Page
 
-The redirection page for Single Sign-On is available at `<IS-HOME>/repository/resources/identity/pages/samlsso_response.html`.Edit this HTML file to re-brand the SSO redirection page.
+The redirection page for Single Sign-On is available at `<IS_HOME>/repository/resources/identity/pages/samlsso_response.html`.Edit this HTML file to re-brand the SSO redirection page.
 
 Additionally, you can use some variable placeholders inside this HTML
 file to enhance your customization. These placeholders are replaced with