Minor Improvement

Author: nermalcat69

apps/docs/content/dotnet/how-to/access.mdx

@@ -10,7 +10,7 @@ Services can be of different types (runtime services, databases, message brokers
 To connect to your application with `app` hostname running on [internal port](/dotnet/how-to/build-pipeline#ports) `5000`, simply use `http://app:5000`
 
 :::info
-Do not use <code>https://</code> when communicating with .NET from other runtime services in the same project. The internal communication is done over a private network and is isolated from other projects.
+Do not use `https://` when communicating with .NET from other runtime services in the same project. The internal communication is done over a private network and is isolated from other projects.
 :::
 
 ### Use .NET environment variables
@@ -41,12 +41,12 @@ You can securely connect to your .NET application from your local workspace via
 Once the VPN session is established, you have the secured connection to the project's private network in Zerops. You can access all project services locally by using their hostname. The only difference is that no [environment variables](/dotnet/how-to/env-variables) are available when connected through VPN. To connect to your .NET application in Zerops set the hostname and [internal port](/dotnet/how-to/build-pipeline#ports) e.g. http://app:5000
 
 :::info
-Do not use <code>https://</code> when communicating with .NET over the VPN. The security is assured by the VPN. The internal communication is done over a private network and is isolated from other projects.
+Do not use `https://` when communicating with .NET over the VPN. The security is assured by the VPN. The internal communication is done over a private network and is isolated from other projects.
 :::
 
 ### Connect via SSH
 
-Use the <a href="/references/ssh"><code>ssh</code> command</a> to connect to your service via SSH.
+Use the <a href="/references/ssh">`ssh` command</a> to connect to your service via SSH.
 
 ### Stop VPN connection
 

apps/docs/content/dotnet/how-to/build-pipeline.mdx

@@ -117,7 +117,7 @@ zerops:
 <p>
   The base build environment contains {data.alpineCurrentVersion}, the selected
   major version of .NET, <a href="/references/cli">Zerops command line tool</a>,{' '}
-  <code>ASP .NET</code> and <code>git</code>.
+  `ASP .NET` and `git`.
 </p>
 
 :::info
@@ -290,7 +290,7 @@ If the command ends successfully, it returns the exit code 0 and Zerops triggers
 
 ### deployFiles
 
-_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use <a href="#deployignore"><code>.deployignore</code></a> file.
+_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use <a href="#deployignore">`.deployignore`</a> file.
 
 ```yml
 # REQUIRED. Select which files / folders to deploy after
@@ -351,7 +351,7 @@ deployFiles: ./path/~/to/
 
 #### .deployignore
 
-Add a `.deployignore` file to the root of your project and specify which files and folders Zerops should ignore during deploy. The syntax is the same as of a <a href="https://git-scm.com/docs/gitignore#_pattern_format"><code>.gitignore</code></a> file.
+Add a `.deployignore` file to the root of your project and specify which files and folders Zerops should ignore during deploy. The syntax is the same as of a <a href="https://git-scm.com/docs/gitignore#_pattern_format">`.gitignore`</a> file.
 
 Example to ignore `src/file.txt` file in deploy:
 
@@ -367,7 +367,7 @@ src / file.txt;
 ```
 
 :::note
-`.deployignore` file also works with <a href="/references/cli/commands#deploy"><code>zcli service deploy</code></a> command.
+`.deployignore` file also works with <a href="/references/cli/commands#deploy">`zcli service deploy`</a> command.
 :::
 
 ### cache
@@ -518,7 +518,7 @@ _OPTIONAL._ Customises the .NET runtime environment by installing additional dep
 <p>
   The base .NET environment contains {data.alpineCurrentVersion}, the selected
   major version of .NET, <a href="/references/cli">Zerops command line tool</a>{' '}
-  and <code>ASP .NET</code> and <code>git</code>. To install additional packages
+  and `ASP .NET` and `git`. To install additional packages
   or tools add one or more prepare commands:
 </p>
 
@@ -573,7 +573,7 @@ You can configure your prepare commands to be run in a single shell instance or
   The prepare runtime container contains {data.alpineCurrentVersion}, the
   selected major version of .NET,{' '}
   <a href="/references/cli">Zerops command line tool</a> and{' '}
-  <code>ASP .NET</code> and <code>git</code>.
+  `ASP .NET` and `git`.
 </p>
 
 The prepare runtime container does not contain your application code nor the built application. If you need to copy some folders or files from the build container to the runtime container (e.g. a configuration file) use the `addToRunPrepare` attribute in the [build section](#build-pipeline-configuration).

apps/docs/content/dotnet/how-to/build-process.mdx

@@ -44,7 +44,7 @@ The default .NET build environment contains:
 - [zCLI](/references/cli), Zerops command line tool
 - ASP .NET`and`git`
 
-If you prefer the Ubuntu OS instead of Alpine, set the <code><a href="/dotnet/how-to/build-pipeline#os">build.os</a></code> attribute to `ubuntu`. To install additional packages or tools add one or more [build.prepareCommands](/dotnet/how-to/build-pipeline#preparecommands) commands to your `zerops.yml`.
+If you prefer the Ubuntu OS instead of Alpine, set the `<a href="/dotnet/how-to/build-pipeline#os">build.os</a>` attribute to `ubuntu`. To install additional packages or tools add one or more [build.prepareCommands](/dotnet/how-to/build-pipeline#preparecommands) commands to your `zerops.yml`.
 
 :::info
 The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).

apps/docs/content/dotnet/how-to/create.mdx

@@ -268,7 +268,7 @@ At least one service in `services:` section is required. You can create a projec
         <br />
         <br />
         The hostname of the new database will be set to the{' '}
-        <code>hostname</code> value. <br />
+        `hostname` value. <br />
         <br />
         <b>Limitations:</b>
         <br />- duplicate services with the same name in the same project are
@@ -283,16 +283,16 @@ At least one service in `services:` section is required. You can create a projec
         <b>type</b>
       </td>
       <td>
-        Specifies the service type <code>dotnet</code> and version.
+        Specifies the service type `dotnet` and version.
         <br />
         Set type:{' '}
-        <code>
+        `
           dotnet<span>@</span>&lt;version&gt;
-        </code>{' '}
+        `{' '}
         or{' '}
-        <code>
+        `
           dotnet<span>@</span>latest
-        </code>
+        `
         <br />
         <br />
         <b>Limitations:</b>
@@ -319,8 +319,8 @@ At least one service in `services:` section is required. You can create a projec
         <b> - cpuMode</b>
       </td>
       <td>
-        <b>Optional.</b> Accepts <code>SHARED</code>, <code>DEDICATED</code>{' '}
-        values. Default is <code>SHARED</code>
+        <b>Optional.</b> Accepts `SHARED`, `DEDICATED`{' '}
+        values. Default is `SHARED`
       </td>
     </tr>
     <tr>

apps/docs/content/dotnet/how-to/customize-runtime.mdx

@@ -18,12 +18,12 @@ The default .NET runtime environment contains:
 - <span>{data.alpineCurrentVersion}</span>
 - selected version of .NET selected when the runtime service was created.
 - <a href="/references/cli">
-    <code>zCLI</code>
+    `zCLI`
   </a>
   , Zerops command line tool
 - ASP .NET`and`git`
 
-If you prefer the Ubuntu OS instead of Alpine, set the <code><a href="/dotnet/how-to/build-pipeline#os">build.os</a></code> attribute to `ubuntu`. To install additional packages or tools add one or more <a href="/dotnet/how-to/build-pipeline#preparecommands-1"><code>run.prepareCommands</code></a> commands to your `zerops.yml`.
+If you prefer the Ubuntu OS instead of Alpine, set the `<a href="/dotnet/how-to/build-pipeline#os">build.os</a>` attribute to `ubuntu`. To install additional packages or tools add one or more <a href="/dotnet/how-to/build-pipeline#preparecommands-1">`run.prepareCommands`</a> commands to your `zerops.yml`.
 
 When the first deploy with a defined `prepareCommands` attribute is triggered, Zerops will
 
@@ -41,7 +41,7 @@ The prepare runtime container is automatically deleted after the prepare runtime
 
 Some packages or tools can take a long time to install. Therefore, Zerops caches your custom runtime environment after the installation of your custom packages or tools is completed. When the second or following deploy is triggered, Zerops will use the custom runtime cache from the previous deploy if following conditions are met:
 
-1. Content of the <a href="/dotnet/how-to/build-pipeline#copy-folders-or-files-from-your-build-container"><code>build.addToRunPrepare</code></a> and <a href="/dotnet/how-to/build-pipeline#preparecommands-1"><code>run.prepareCommands</code></a> attributes didn't change from the previous deploy
+1. Content of the <a href="/dotnet/how-to/build-pipeline#copy-folders-or-files-from-your-build-container">`build.addToRunPrepare`</a> and <a href="/dotnet/how-to/build-pipeline#preparecommands-1">`run.prepareCommands`</a> attributes didn't change from the previous deploy
 2. The custom runtime cache wasn't invalidated in the Zerops GUI.
 
 To invalidate the custom runtime cache go to `yyy`

apps/docs/content/dotnet/how-to/deploy-process.mdx

@@ -39,11 +39,11 @@ Zerops performs following actions for each new container:
 Services with multiple containers are deployed in parallel.
 
 :::info
-If your application needs to be initialized in each runtime container, add [init commands](/dotnet/how-to/build-pipeline#initcommands) to <code>zerops.yml</code>.
+If your application needs to be initialized in each runtime container, add [init commands](/dotnet/how-to/build-pipeline#initcommands) to `zerops.yml`.
 :::
 
 :::caution
-Do not use the <code>initCommands</code> for customising your runtime environment. See [how to customise the runtime environment](/dotnet/how-to/deploy-process#customise-dotnet-runtime-environment).
+Do not use the `initCommands` for customising your runtime environment. See [how to customise the runtime environment](/dotnet/how-to/deploy-process#customise-dotnet-runtime-environment).
 :::
 
 ## Further deploys
@@ -70,9 +70,9 @@ Application in the runtime container with a pending readiness check won't receiv
 
 If the readiness check is still failing after 5 minutes, the specific runtime container is marked as failed and Zerops will delete it, create a new runtime container and perform the deploy.
 
-The <a href="/dotnet/how-to/build-pipeline#httpget"><code>httpGet</code></a> readiness check is successful when the URL returns HTTP status code `2xx`. The timeout is 5 seconds. When the URL returns a `3xx` HTTP status, the readiness check HTTP client will follow the redirect.
+The <a href="/dotnet/how-to/build-pipeline#httpget">`httpGet`</a> readiness check is successful when the URL returns HTTP status code `2xx`. The timeout is 5 seconds. When the URL returns a `3xx` HTTP status, the readiness check HTTP client will follow the redirect.
 
-The <a href="/dotnet/how-to/build-pipeline#exec"><code>exec.command</code></a> readiness check is successful when the command returns status code 0. The timeout is 5 seconds.
+The <a href="/dotnet/how-to/build-pipeline#exec">`exec.command`</a> readiness check is successful when the command returns status code 0. The timeout is 5 seconds.
 
 Read the [runtime log](/dotnet/how-to/logs#runtime-log) to troubleshoot failed readiness checks.
 

apps/docs/content/dotnet/how-to/logs.mdx

@@ -88,11 +88,11 @@ app.Logger.LogInformation('<7>Debug (7) severity > debug-level message.');
 
 :::info
 
-<code>logger.LogTrace</code>, <code>logger.LogInformation</code>,
-<code>logger.LogWarning</code>, <code>logger.LogDebug</code>, <code>
+`logger.LogTrace`, `logger.LogInformation`,
+`logger.LogWarning`, `logger.LogDebug`, `
   logger.LogError
-</code> and <code>logger.LogCritical</code> are just aliases to the <code>
+` and `logger.LogCritical` are just aliases to the `
   logger.LogInformation
-</code> method. They don't set the appropriate severity number. Use the <code>
+` method. They don't set the appropriate severity number. Use the `
   &lt;N&gt;
-</code> prefix instead. :::
+` prefix instead. :::

apps/docs/content/dotnet/how-to/trigger-pipeline.mdx

@@ -34,7 +34,7 @@ Then each time you create a new tag or push to a specific branch, depending on t
 </p>
 
 :::info
-You can change the build and deploy pipeline when you need to. Just simply modify the <code>zerops.yml</code> in your repository.
+You can change the build and deploy pipeline when you need to. Just simply modify the `zerops.yml` in your repository.
 :::
 
 ### Skip the automatic pipeline once
@@ -60,7 +60,7 @@ To start a new build & deploy pipeline manually, use the Zerops CLI.
 
 Follow these steps:
 
-1. Add <a href="/dotnet/how-to/build-pipeline#add-zeropsyml-to-your-repository"><code>zerops.yml</code></a> to your repository.
+1. Add <a href="/dotnet/how-to/build-pipeline#add-zeropsyml-to-your-repository">`zerops.yml`</a> to your repository.
 2. [Install & setup zCLI](/references/cli) the Zerops command line tool.
 3. Run `zcli push` command.
 
@@ -96,7 +96,7 @@ Flags:
 zCLI commands are interactive, when you press enter after `zcli push`, you will be given a list of your projects to choose from.
 
 :::info
-You can change the build and deploy pipeline when you need to. Just simply modify the <code>zerops.yml</code> in your repository.
+You can change the build and deploy pipeline when you need to. Just simply modify the `zerops.yml` in your repository.
 :::
 
 ## Manual deploy using Zerops CLI
@@ -138,5 +138,5 @@ Flags:
 `zerops.yml` must be placed in the working directory.
 
 :::info
-You can change the deploy pipeline when you need to. Just simply modify the <code>zerops.yml</code> in your working directory.
+You can change the deploy pipeline when you need to. Just simply modify the `zerops.yml` in your working directory.
 :::

apps/docs/content/dotnet/how-to/upgrade.mdx

@@ -2,6 +2,6 @@
 title: How to upgrade the .NET version
 ---
 
-You can upgrade or downgrade your .NET service to a different major .NET version by setting the <a href="/dotnet/how-to/build-pipeline#base-1"><code>run.base</code></a> parameter in your `zerops.yml`. When you [trigger a new pipeline](/dotnet/how-to/trigger-pipeline), Zerops will start new runtime container(s) with the required .NET version. If you don't specify the `run.base` attribute in your `zerops.yml`, Zerops keeps the current .NET version for your runtime.
+You can upgrade or downgrade your .NET service to a different major .NET version by setting the <a href="/dotnet/how-to/build-pipeline#base-1">`run.base`</a> parameter in your `zerops.yml`. When you [trigger a new pipeline](/dotnet/how-to/trigger-pipeline), Zerops will start new runtime container(s) with the required .NET version. If you don't specify the `run.base` attribute in your `zerops.yml`, Zerops keeps the current .NET version for your runtime.
 
-If you want to build your application with a different major .NET version, change the <a href="/dotnet/how-to/build-pipeline#base"><code>build.base</code></a> parameter in your `zerops.yml`. The `build.base` is the required attribute.
+If you want to build your application with a different major .NET version, change the <a href="/dotnet/how-to/build-pipeline#base">`build.base`</a> parameter in your `zerops.yml`. The `build.base` is the required attribute.

apps/docs/content/dotnet/tutorial/quickstart.mdx

@@ -29,7 +29,7 @@ services:
 **That's it, your application is now up and running! :star: Let's check it works:**
 
 1. A _subdomain_ should have been enabled and visible in the project's **IP addressed & Public Routing Overview** box. Its format should look similar to this `https://helloworld-24-8080.prg1.zerops.app`.
-2. Click or the <code>subdomain</code> URL to open it in a browser and you should see
+2. Click or the `subdomain` URL to open it in a browser and you should see
 
 ```
 Hello, World!