Update network-file-system-protocol-support-how-to.md

Removed references to mounting in /mnt as this conflicts with the azure resource disk.  
Added fstab information

Author: pagienge

articles/storage/blobs/network-file-system-protocol-support-how-to.md

@@ -75,31 +75,39 @@ Create a directory on your Linux system, and then mount the container in the sto
 1. On your Linux system, create a directory:
 
    ```
-   mkdir -p /mnt/test
+   mkdir -p /nfsdata
    ```
 
-2. Mount the container by using the following command:
-
-   ```
-   mount -o sec=sys,vers=3,nolock,proto=tcp <storage-account-name>.blob.core.windows.net:/<storage-account-name>/<container-name>  /mnt/test
-   ```
-
-   - Replace the `<storage-account-name>` placeholder that appears in this command with the name of your storage account.
-
-   - Replace the `<container-name>` placeholder with the name of your container.
+2. Mount the container by one of the following methods:
+    - In both methods replace the `<storage-account-name>` placeholder with the name of your storage account and `<container-name>` with the name of your container.
+
+    - To have the share mounted automatically on reboot
+        - create an entry in the /etc/fstab file by adding the following line
+        ```
+        <storage-account-name>.blob.core.windows.net:/<storage-account-name>/<container-name>  /nfsdata    nfs defaults,sec=sys,vers=3,nolock,proto=tcp,nofail    0 0
+        ```
+        - Run the following command to immediately process the /etc/fstab entries and attempt mount the above path
+        ```
+        mount /nfsdata
+        ```
+        
+    - For a temporary mount which will not persist across reboots
+        ```
+        mount -o sec=sys,vers=3,nolock,proto=tcp <storage-account-name>.blob.core.windows.net:/<storage-account-name>/<container-name>  /nfsdata
+        ```
 
 ## Resolve common errors
 
 |Error | Cause/resolution|
 |---|---|
 |`Access denied by server while mounting`|Ensure that your client is running within a supported subnet. See [Supported network locations](network-file-system-protocol-support.md#supported-network-connections).|
 |`No such file or directory`| Make sure to type, rather than copy and paste, the mount command and its parameters directly into the terminal. If you copy and paste any part of this command into the terminal from another application, hidden characters in the pasted information might cause this error to appear. This error also might appear if the account isn't enabled for NFS 3.0.|
-|`Permission denied`| The default mode of a newly created NFS 3.0 container is 0750. Non-root users don't have access to the volume. If access from non-root users is required, root users must change the mode to 0755. Sample command: `sudo chmod 0755 /mnt/<newcontainer>`|
+|`Permission denied`| The default mode of a newly created NFS 3.0 container is 0750. Non-root users don't have access to the volume. If access from non-root users is required, root users must change the mode to 0755. Sample command: `sudo chmod 0755 /nfsdata`|
 |`EINVAL ("Invalid argument"`) |This error can appear when a client attempts to:<li>Write to a blob that was created from a blob endpoint.<li>Delete a blob that has a snapshot or is in a container that has an active WORM (write once, read many) policy.|
 |`EROFS ("Read-only file system"`) |This error can appear when a client attempts to:<li>Write to a blob or delete a blob that has an active lease.<li>Write to a blob or delete a blob in a container that has an active WORM policy. |
 |`NFS3ERR_IO/EIO ("Input/output error"`) |This error can appear when a client attempts to read, write, or set attributes on blobs that are stored in the archive access tier. |
 |`OperationNotSupportedOnSymLink` error| This error can be returned during a write operation via a Blob Storage or Azure Data Lake Storage Gen2 API. Using these APIs to write or delete symbolic links that are created by using NFS 3.0 is not allowed. Make sure to use the NFS 3.0 endpoint to work with symbolic links. |
-|`mount: /mnt/test: bad option;`| Install the NFS helper program by using `sudo apt install nfs-common`.|
+|`mount: /nfsdata: bad option;`| Install the NFS helper program by using `sudo apt install nfs-common`.|
 
 ## See also