Skip to content

Commit e5eeb31

Browse files
committed
hpc-cache: review feedback 1
1 parent 01783f3 commit e5eeb31

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/hpc-cache/hpc-cache-add-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Steps to add the RBAC roles:
7474
1. In the **Select** field, search for "hpc". This string should match one service principal, named "HPC Cache Resource Provider". Click that principal to select it.
7575

7676
> [!NOTE]
77-
> If a search for "hpc" doesn't work, try using the string "storagecache" instead. Users who joined the previews (before GA) might need to use the older name for the service principal.
77+
> If a search for "hpc" doesn't work, try using the string "storagecache" instead. Users who participated in previews (before GA) might need to use the older name for the service principal.
7878
7979
1. Click the **Save** button at the bottom.
8080

@@ -124,7 +124,7 @@ When finished, click **OK** to add the storage target.
124124
### Choose a usage model
125125
<!-- referenced from GUI - update aka.ms link if you change this heading -->
126126

127-
When you create a storage target that points to an NFS storage system, you need to choose the *usage model* for that target. This model determines how your data is cached.
127+
When you create a storage target that points to an NFS storage system, you need to choose the usage model for that target. This model determines how your data is cached.
128128

129129
There are three options:
130130

articles/hpc-cache/hpc-cache-mount.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: rohogue
1010

1111
# Mount the Azure HPC Cache
1212

13-
After the cache is created, NFS clients can access it with a simple mount command. The command connects a specific storage target path on the Azure HPC Cache to a local directory on the client machine.
13+
After the cache is created, NFS clients can access it with a simple `mount` command. The command connects a specific storage target path on the Azure HPC Cache to a local directory on the client machine.
1414

1515
The mount command is made up of these elements:
1616

@@ -19,7 +19,7 @@ The mount command is made up of these elements:
1919
* The local path to use on the client
2020
* Command parameters that optimize the success of this kind of NFS mount
2121

22-
The **Mount instructions** page for your cache collects the information and the recommended options for you, and creates a prototype mount command that you can copy. Read [Use the mount instructions utility](#use-the-mount-instructions-utility), below, for details.
22+
The **Mount instructions** page for your cache collects the information and the recommended options for you, and creates a prototype mount command that you can copy. Read [Use the mount instructions utility](#use-the-mount-instructions-utility) for details.
2323

2424
## Prepare clients
2525

@@ -54,13 +54,13 @@ The mount command page includes information about the client mount process and p
5454

5555
To use this page, follow this procedure:
5656

57-
1. Review the client prerequisites and install the utilities needed to use the NFS `mount` command as described above in [Prepare clients](#prepare-clients).
58-
5957
<!--1. In step one of **Mounting your file system**, enter the path that the client will use to access the Azure HPC Cache storage target.
6058
6159
* This path is local to the client.
6260
* After you provide the directory name, the field populates with a command you can copy. Use this command on the client directly or in a setup script to create the directory path on the client VM. -->
6361

62+
1. Review the client prerequisites and install the utilities needed to use the NFS `mount` command as described above in [Prepare clients](#prepare-clients).
63+
6464
1. Step one of **Mounting your file system**<!-- label will change --> gives an example command for creating the local path on the client. This is the path that the client will use to access the content from the Azure HPC Cache.
6565

6666
Note the path name so that you can modify it in the command if needed.

0 commit comments

Comments
 (0)