diff --git a/README.md b/README.md
index ab172a94..219d16a9 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 [![codecov](https://codecov.io/gh/center-for-threat-informed-defense/attack-control-framework-mappings/branch/master/graph/badge.svg?token=PLVBGOUWMC)](https://codecov.io/gh/center-for-threat-informed-defense/attack-control-framework-mappings)
 
 # Security Control Framework Mappings to ATT&CK
-This repository contains security control framework mappings to MITRE ATT&CK® with supporting documentation and resources. These mappings provide a critically important resource for organizations to assess their security control coverage against real-world threats as described in the ATT&CK knowledge base and provide a foundation for integrating ATT&CK-based threat information into the risk management process. This work was developed by the [Center for Threat-Informed Defense](https://mitre-engenuity.org/center-for-threat-informed-defense/) in collaboration with our participants.
+This repository contains security control framework mappings to MITRE ATT&CK® with supporting documentation and resources. These mappings provide a critically important resource for organizations to assess their security control coverage against real-world threats as described in the ATT&CK knowledge base and provide a foundation for integrating ATT&CK-based threat information into the risk management process. This work was developed by the [Center for Threat-Informed Defense](https://ctid.mitre-engenuity.org/) in collaboration with our participants.
 
 **NIST 800-53 Revision 4 Security Control Mappings**
 
diff --git a/docs/mapping_methodology.md b/docs/mapping_methodology.md
index a36b016b..92a8d433 100644
--- a/docs/mapping_methodology.md
+++ b/docs/mapping_methodology.md
@@ -54,7 +54,7 @@ To continue with the example, further review and analysis confirms the identifie
 
 ## Applying the Methodology
 
-This methodology is designed to be tailored as it is applied to security control frameworks. We anticipate that each framework will require its own unique mapping and scoping decisions. These framework specific decisions should be documented in the ReadMe for the framework. As an example, see the [Mapping NIST 800-53 revision 4 to ATT&CK](/frameworks/nist800-53-r4#mapping-nist-800-53-revision-4-to-attck) section of the NIST 800-53 Rev. 4 mapping documentation. 
+This methodology is designed to be tailored as it is applied to security control frameworks. We anticipate that each framework will require its own unique mapping and scoping decisions. These framework specific decisions should be documented in the ReadMe for the framework. As an example, see the [Mapping NIST 800-53 revision 4 to ATT&CK](/frameworks/ATT%26CK-v8.2/nist800-53-r4#mapping-nist-800-53-revision-4-to-attck) section of the NIST 800-53 Rev. 4 mapping documentation. 
 
 ## References