Fixing anchors

Author: DCtheGeek

articles/security-center/recommendations-reference.md

@@ -66,7 +66,7 @@ Your Secure Score is based on the number of Security Center recommendations you'
 |**Least privileged Linux capabilities should be enforced for containers**|To reduce attack surface of your container, restrict Linux capabilities and grant specific privileges to containers without granting all the privileges of the root user.<br>We recommend dropping all capabilities, then adding those that are required.<br>(Related policy: [Preview]: Kubernetes cluster containers should only use allowed capabilities)|Medium|N|Kubernetes Service|
 |**Overriding or disabling of containers AppArmor profile should be restricted**|Containers running on your Kubernetes cluster should be limited to allowed AppArmor profiles only.<br>AppArmor (Application Armor) is a Linux security module that protects an operating system and its applications from security threats. To use it, a system administrator associates an AppArmor security profile with each program. <br>(Related policy: [Preview]: Kubernetes cluster containers should only use allowed AppArmor profiles)|High|N|Kubernetes Service|
 |**Privileged containers should be avoided**|To prevent unrestricted host access, avoid privileged containers whenever possible.<br>Privileged containers have all of the root capabilities of a host machine. They can be used as entry points for attacks, and to spread malicious code or malware to compromised applications, hosts, and networks. <br>(Related policy: [Preview]: Do not allow privileged containers in Kubernetes cluster)|Medium|N|Kubernetes Service|
-|**Role-Based Access Control should be used to restrict access to a Kubernetes Service Cluster**|To provide granular filtering of the actions that users can perform, use Role-Based Access Control (RBAC) to manage permissions in Kubernetes Service Clusters and configure relevant authorization policies. For more information see [Azure role-based access control](../aks/concepts-identity.md#role-based-access-controls-rbac).<br>(Related policy: [Preview]: Role-Based Access Control (RBAC) should be used on Kubernetes Services)|Medium|N|Kubernetes Service|
+|**Role-Based Access Control should be used to restrict access to a Kubernetes Service Cluster**|To provide granular filtering of the actions that users can perform, use Role-Based Access Control (RBAC) to manage permissions in Kubernetes Service Clusters and configure relevant authorization policies. For more information see [Azure role-based access control](../aks/concepts-identity.md#azure-role-based-access-control-azure-rbac).<br>(Related policy: [Preview]: Role-Based Access Control (RBAC) should be used on Kubernetes Services)|Medium|N|Kubernetes Service|
 |**Running containers as root user should be avoided**|Containers should run as a non-root users in your Kubernetes cluster. <br>Running a process as the root user inside a container runs it as root on the host. <br>In case of compromise, an attacker has root in the container, and any misconfigurations become easier to exploit.<br>(Related policy: [Preview]: Kubernetes cluster containers should run as a non-root users)|High|N|Kubernetes Service|
 |**Services should listen on allowed ports only**|To reduce the attack surface of your Kubernetes cluster, restrict access to the cluster by limiting services’ access to the configured ports.. <br>(Related policy: [Preview]: Ensure services listen only on allowed ports in Kubernetes cluster)|Medium|N|Kubernetes Service|
 |**The Kubernetes Service should be upgraded to the latest Kubernetes version**|Upgrade Azure Kubernetes Service clusters to the latest Kubernetes version in order to benefit from up-to-date vulnerability patches. For details regarding specific Kubernetes vulnerabilities see [Kubernetes CVEs](https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=kubernetes).<br>(Related policy: [Preview]: Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version)|High|N|Kubernetes Service|

articles/security-center/secure-score-security-controls.md

@@ -206,7 +206,7 @@ The table below lists the security controls in Azure Security Center. For each c
 No. It won't change until you remediate all of the recommendations for a single resource. To get the maximum score for a control, you must remediate all recommendations, for all resources.
 
 ### If a recommendation isn't applicable to me, and I disable it in the policy, will my security control be fulfilled and my secure score updated?
-Yes. We recommend disabling recommendations when they're inapplicable in your environment. For instructions on how to disable a specific recommendation, see [Disable security policies](./tutorial-security-policy.md#disable-security-policies).
+Yes. We recommend disabling recommendations when they're inapplicable in your environment. For instructions on how to disable a specific recommendation, see [Disable security policies](./tutorial-security-policy.md#disable-security-policies-and-disable-recommendations).
 
 ### If a security control offers me zero points towards my secure score, should I ignore it?
 In some cases, you'll see a control max score greater than zero, but the impact is zero. When the incremental score for fixing resources is negligible, it's rounded to zero. Don't ignore these recommendations as they still bring security improvements. The only exception is the "Additional Best Practice" control. Remediating these recommendations won't increase your score, but it will enhance your overall security.