diff --git a/main/access-models.md b/main/access-models.md
index 42aa6b8..90d159a 100755
--- a/main/access-models.md
+++ b/main/access-models.md
@@ -1,7 +1,7 @@
 
 # Access models for the service
 
-There are currently two ways in which you can make use of the Nextflow Seqera service:
+There are currently two ways in which you can make use of the Australian Nextflow Seqera Service:
 
 ## 1. Organisation workspace
 
@@ -17,20 +17,20 @@ Organisation workspaces are private and their resources are only accessible by t
 - Organisation workspace can be shared where all their resources become accessible to all users in the Australian BioCommons Organisation on Australian Nextflow Seqera platform. This kind of workspace can be very effective to share pipelines to benefit the broader Bioinformatics community. Check Seqera documentation to undestand more about [shared worksapces](https://docs.seqera.io/latest/orgs-and-teams/shared-workspaces/).
 
 > **Important:**
-> please reach out to the Australian BioCommons if you plan to utilise this kind of workspaces.
+> Please reach out to the Australian BioCommons if you plan to utilise this kind of workspace.
 
 > **Organisaion workspace Support:**
-> Check out the [support webpage](/main/support.md) to undestand more on the available support to this access model.
+> Check out the [support page](/main/support.md) to undestand more on the available support for this access model.
 
 
 ## 2. Personal workspace
-Any Australian researcher can access [the Australian BioCommons Seqera Service](http://seqera.services.biocommons.org.au/) and use their own personal workspace for their work. Please refer to the [Seqera documentation](https://docs.seqera.io/latest/getting-started/workspace/). 
+Any Australian researcher can access [the Australian BioCommons Nextflow Seqera Service](http://seqera.services.biocommons.org.au/) and use their own personal workspace. Please refer to the [Seqera documentation](https://docs.seqera.io/latest/getting-started/workspace/). 
 
 Note:
 
-- Personal workspaces are only accessible by their owners,
+- Personal workspaces are only accessible by their owners.
 
-- The Australian BioCommons does not provide direct support for this model
+- The Australian BioCommons does not provide direct support for this model.
 
 - Users are responsible for setting up, managing and maintaining their workspaces. 
 
@@ -41,4 +41,4 @@ Note:
 
 <br/>
 <div style="text-align:center"><img width="50%" src="../assets/doc_img/seqera-process.png"/></div>
-<br/>
\ No newline at end of file
+<br/>
diff --git a/user-guide/compute-env.md b/user-guide/compute-env.md
index 85dfe67..a35eebc 100755
--- a/user-guide/compute-env.md
+++ b/user-guide/compute-env.md
@@ -9,7 +9,7 @@ page_id: pg-3
 
 ## Introduction
 
-Seqera supports running pipelines on several compute platforms including commercial cloud such as AWS and Azure, as well as high-performance computer (HPC). A full list of supported platforms is available through [Seqera documenation] (https://docs.seqera.io/latest/compute-envs/overview/). 
+Seqera supports running pipelines on several compute platforms including commercial cloud such as AWS and Azure, as well as high-performance computer (HPC). A full list of supported platforms is available through [Seqera documentation](https://docs.seqera.io/latest/compute-envs/overview/). 
 
 To access these compute infrastructures through Seqera, compute environments need to be created and configured on Seqera for each compute infrastructure.
 
@@ -25,9 +25,9 @@ In order to access compute infrastructre, you need to create access [credentials
 The following instructions is to configure compute invirnment for HPC through Tower agent credentials.
 
 
-### Steps to configure HPC on the Australian Nextflow Seqera Service within organisation workspace
+### Steps to configure HPC on the Australian Nextflow Seqera Service within an organisation workspace
 
-Prerequisites for configuration on organisation workspace:
+Prerequisites for configuration on an organisation workspace:
 
 1.	You have access to an organisation workspace
 2.	The user has an owner or admin role within this workspace.
@@ -54,10 +54,10 @@ The following steps need to be completed in order unless they have been complete
             You don’t need an access token if you intend to create SSH key credentials, but you will need it for the Tower agent credentials. 
             <ul>
             <li>The user can create an access token as <a href="https://docs.seqera.io/latest/api/overview/?h=access+token#authentication"> described here </a>.</li>
-            <li>Keep it safe, create a new one if you lose it and delete lost tokens</li>
+            <li>Keep it safe, create a new one if you lose it and delete lost tokens.</li>
             <li>Use descriptive names.</li>
             <li>Don’t share your token with others.</li>
-            <li>After you close the token creation window, you will not be able to view/copy the Token any more, but you can update it or delete it.</li>
+            <li>After you close the token creation window, you will not be able to view/copy the token any more, but you can update it or delete it.</li>
             </ul>
             <div class="alert alert-primary" role="alert">
             <h4 class="alert-heading">Note</h4>
@@ -170,7 +170,7 @@ The following steps need to be completed in order unless they have been complete
 </div>
 
 
-### Utilising Compute envornment with tower agent
+### Utilising compute environment with tower agent
 
 There are few points to be considered when using tower agent
 
@@ -193,9 +193,11 @@ To do that:
      <p>The agent should be able to access the internet.</p>
 </div>
 
-## Configuring Commerical cloud
+## Configuring commerical cloud
 
 The easiest way is using AWS Batch and tower forge permissions to allow tower to create the batch environment. In order to do this please follow this [documentation](https://docs.seqera.io/latest/compute-envs/aws-batch/).
 
-Other Compute infrastructures such Azure and others: Please visit [Seqera documentation](https://docs.seqera.io/latest/compute-envs/overview/) for more details.
- 
\ No newline at end of file
+## Other infrastructures
+
+Please visit [Seqera documentation](https://docs.seqera.io/latest/compute-envs/overview/) for more details on configuring for other compute infrastructures such as Azure.
+ 
diff --git a/user-guide/service-access.md b/user-guide/service-access.md
index 58a5680..d2daf1f 100755
--- a/user-guide/service-access.md
+++ b/user-guide/service-access.md
@@ -9,7 +9,7 @@ page_id: pg-1
 
 ## Access an organisation workspace
 
-Accessing an organisation workspace requires joining the [pilot project of the Australian Nextflow Seqera Service](/main/join_us.md) as described.
+Accessing an organisation workspace requires joining the [pilot project of the Australian Nextflow Seqera Service](/main/nextflowseqera/join_us.md).
 
 Under the pilot project, you can:
 
@@ -25,7 +25,7 @@ Under the pilot project, you can:
 
 ## Join an existing organisation workspace
 
-1. The user who needs to access a workspace should log in to the Australian Nextflow Seqera service. 
+1. The user who needs to access a workspace should log in to the Australian Nextflow Seqera Service. 
 
 2. The email address used in the user’s login should then be shared with the admin of the workspace and the admin can add the user directly as described in Seqera documentation here. This should be done under the participants' tab in the workspace rather than the organisation.
 
@@ -36,4 +36,4 @@ Visit [Seqera documentation](https://docs.seqera.io/latest/orgs-and-teams/worksp
 
 ## Access a personal workspace
 
-By default, each user on the Australian  Nextflow Seqera service will have their own personal workspace which can be accessed directly after logging into the service. No need to contact the Australian BioCommons to use your own personal workspace. This model is not supported by the Australian BioCommons at this stage, and users are responsible to configure and use their personal workspace.
+By default, each user on the Australian  Nextflow Seqera Service will have their own personal workspace which can be accessed directly after logging into the service. There is no need to contact the Australian BioCommons to use your own personal workspace. This model is not currently supported, and users are responsible to configure and use their personal workspace.