From 260fa6d66defdca7bf12c52bbfcfc9a3e80d34c7 Mon Sep 17 00:00:00 2001
From: Davide Marchegiani <davide.marchegiani@gmail.com>
Date: Mon, 14 Oct 2024 10:16:23 +1100
Subject: [PATCH] Added Harshula's suggestions.

---
 docs/models/run-a-model/build_a_model.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/models/run-a-model/build_a_model.md b/docs/models/run-a-model/build_a_model.md
index d432a8def..f5928190a 100644
--- a/docs/models/run-a-model/build_a_model.md
+++ b/docs/models/run-a-model/build_a_model.md
@@ -98,7 +98,7 @@ spack env activate -p mom5_dev
 
 ## Compile Spack environment packages (optional)
 
-It is recommended to first compile all the packages in the newly created _Spack_ environment as is without making any changes.
+It is recommended to first compile all the packages in the newly created _Spack_ environment as is, without making any changes.
 
 Compiling all the packages present in a _Spack_ environment is referred to as [installing the environment](https://spack.readthedocs.io/en/latest/environments.html#installing-an-environment).
 
@@ -504,11 +504,11 @@ spack install
     The full output has been truncated for brevity.
 
 !!! tip
-  From now on, the source code can be modified and the _Spack_ environment installed without repeating the concretization step.<br>
-  The _Spack_ environment will need to be re-concretized only if further changes occur in the `spack.yaml` file.
+    From now on, the source code can be modified and the _Spack_ environment installed without repeating the concretization step.<br>
+    The _Spack_ environment will need to be re-concretized only if further changes occur in the `spack.yaml` file.
 
 ## Output directory for compiled packages
-For the Spack instance obtained through the [Spack setup instructions]({{spack_setup}}), all compiled packages will be placed in directories having the following format: `<install_tree.root>/{architecture}/{compiler.name}-{compiler.version}/{name}-{version}-{hash}`.
+For the Spack instance obtained through the [Spack setup instructions]({{spack_setup}}), all compiled packages will be placed in directories having the following format: `<install_tree.root>/<architecture>/<compiler.name>-<compiler.version>/<name>-<version>-<hash>`.
 
 `<install_tree.root>` depends on the [`install_tree.root`](https://spack.readthedocs.io/en/latest/config_yaml.html#install-tree-root) configuration field. _Spack_ reads this configuration field from files in several directories, following [Spack's configuration scopes](https://spack.readthedocs.io/en/latest/configuration.html#configuration-scopes).
 
@@ -524,7 +524,7 @@ config:
 !!! tip
     For the _Spack_ instance obtained through the [Spack setup instructions]({{spack_setup}}), `$spack` (referred to as `$(prefix)` in _Spack_ configuration scopes documentation above) corresponds to the `/g/data/$PROJECT/$USER/spack/0.22/spack` directory.
 
-This means the packages built in this example can be found in `/g/data/$PROJECT/$USER/spack/0.22/spack/../restricted/ukmo/release/<architecture>/<compiler>/<package-name>`.
+This means the packages built in this example can be found in `/g/data/$PROJECT/$USER/spack/0.22/spack/../restricted/ukmo/release/<architecture>/<compiler.name>-<compiler.version>/<name>-<version>-<hash>`.
 
 ## Troubleshooting build errors