Improve readability and add TOC entry

Author: ronhogue

articles/hpc-cache/hpc-cache-security-info.md

@@ -16,33 +16,33 @@ This security information applies to Microsoft Azure HPC Cache. It addresses com
 
 The HPC Cache Service is only accessible through your private virtual network. Microsoft cannot access your virtual network.
 
-More information about connecting private networks is available [here](/security/benchmark/azure/baselines/hpc-cache-security-baseline.md).
+Learn more about [connecting private networks](/security/benchmark/azure/baselines/hpc-cache-security-baseline.md).
 
 ## Network infrastructure requirements
 
 Your network needs a dedicated subnet for the Azure HPC Cache, DNS support so the cache can access storage, and access from the subnet to additional Microsoft Azure infrastructure services like NTP servers and the Azure Queue Storage service.
 
-More information about network infrastructure requirements is available [here](hpc-cache-prerequisites.md#network-infrastructure).
+Learn more about [network infrastructure requirements](hpc-cache-prerequisites.md#network-infrastructure).
 
 ## Access to NFS storage
 
 The Azure HPC Cache needs specific NFS configurations like outbound NFS port access to on-premises storage.
 
-For details about configuring your NFS storage to work with Azure HPC Cache, refer to [this article](hpc-cache-prerequisites.md#nfs-storage-requirements).
+Learn more about [configuring your NFS storage](hpc-cache-prerequisites.md#nfs-storage-requirements) to work with Azure HPC Cache.
 
 ## Encryption
 
 HPC Cache data is encrypted at rest. Encryption keys may be Azure-managed or customer-managed.
 
-For more information about implementing customer-managed keys for encrypting data, see [this article](customer-keys.md).
+Learn more about [implementing customer-managed keys](customer-keys.md).
 
 HPC Cache only supports AUTH_SYS security for NFSv3 so it’s not possible to encrypt NFS traffic between clients and the cache. If, however, data is traveling over ExpressRoute, you could [tunnel traffic with IPSEC](../virtual-wan/vpn-over-expressroute.md) for in-transit traffic encryption.
 
 ## Access policies based on IP address
 
 You can set CIDR blocks to allow the following access control policies: none, read, read/write, and squashed.
 
-See the [Access policies](access-policies.md) page for more information about configuring access based on IP addresses.
+Learn more how to [configure access policies](access-policies.md) based on IP addresses.
 
 You can also optionally configure network security groups (NSGs) to control inbound access to the HPC Cache subnet. This restricts which IP addresses are routed to the HPC Cache subnet.
 

articles/hpc-cache/toc.yml

@@ -17,6 +17,8 @@ items:
     items:
     - name: Security baseline
       href: /security/benchmark/azure/baselines/hpc-cache-security-baseline?toc=/azure/hpc-cache/toc.json
+    - name: Security information
+      href: hpc-cache-security-info.md
 - name: How-to guides
   items:
   - name: Prerequisites