refactor(docs): improve formatting and linking on architecture page

This refactors the architecture page to improve readability and navigation. The layout is updated to a single column, the diagram is reoriented, and all components and NIST terms are now linked to their respective pages.

Author: jp-ayyappan

docs/architecture.mdx

@@ -46,37 +46,37 @@ graph TD
     class POLICY,AUTHZ,ERS,KAS opentdfService
     class ATTR_SOURCES,IDP,CLIENT externalSystem
 
-    click POLICY "components/policy/" "Go to Policy Service docs"
-    click AUTHZ "components/authorization" "Go to Authorization Service docs"
-    click ERS "components/entity_resolution" "Go to Entity Resolution Service docs"
-    click KAS "components/key_access" "Go to Key Access Server docs"
+    click POLICY "components/policy/"
+    click AUTHZ "components/authorization"
+    click ERS "components/entity_resolution"
+    click KAS "components/key_access"
 ```
 
 ### [Policy Service](components/policy/)
 
-The **Policy Service** is where all access control policies are defined and managed. It provides the tools and APIs to create a rich set of policies that govern data access. This includes not only attributes and their values, but also the definitions of **actions, obligations, and key access mappings**.
+The Policy Service is where all access control policies are defined and managed. It provides the tools and APIs to create a rich set of policies that govern data access. This includes not only attributes and their values, but also the definitions of **actions, obligations, and key access mappings**.
 
-In the context of the NIST ABAC model, the Policy Service functions as the **Policy Administration Point (PAP)**.
+In the context of the NIST ABAC model, the Policy Service functions as the [Policy Administration Point (PAP)](https://csrc.nist.gov/glossary/term/policy_administration_point).
 
 ### [Authorization Service](components/authorization)
 
-The **Authorization Service** is the core decision-making engine of the platform. It is responsible for evaluating the rich policies from the Policy Service against a set of attributes to render an authorization decision.
+The Authorization Service is the core decision-making engine of the platform. It is responsible for evaluating the rich policies from the Policy Service against a set of attributes to render an authorization decision.
 
-In the context of the NIST ABAC model, it functions as the **Policy Decision Point (PDP)**.
+In the context of the NIST ABAC model, it functions as the [Policy Decision Point (PDP)](https://csrc.nist.gov/glossary/term/policy_decision_point).
 
 ### [Entity Resolution Service (ERS)](components/entity_resolution)
 
-The **Entity Resolution Service** is responsible for gathering the attributes about a subject needed for a decision. By default, it can derive attributes from claims in an authentication token. Optionally, it can be configured to connect to external attribute sources (LDAP, SQL) to "hydrate" the entity with more attributes.
+The Entity Resolution Service is responsible for gathering the attributes about a subject needed for a decision. By default, it can derive attributes from claims in an authentication token. Optionally, it can be configured to connect to external attribute sources (LDAP, SQL) to "hydrate" the entity with more attributes.
 
-In the context of the NIST ABAC model, the ERS functions as the **Policy Information Point (PIP)**.
+In the context of the NIST ABAC model, the ERS functions as the [Policy Information Point (PIP)](https://csrc.nist.gov/glossary/term/policy_information_point).
 
 ### [Key Access Server (KAS)](components/key_access)
 
-The **Key Access Server (KAS)** enforces access control decisions. Its role is more extensive than a typical enforcement point:
+The Key Access Server (KAS) enforces access control decisions. Its role is more extensive than a typical enforcement point:
 
 -   **Cryptographic Enforcement:** It enforces decisions by granting or withholding cryptographic keys for TDF decryption.
 -   **Encryption Enablement:** It manages key exchanges and enables various TDF encryption modes.
 
-In the context of the NIST ABAC model, the KAS functions as the **Policy Enforcement Point (PEP)**.
+In the context of the NIST ABAC model, the KAS functions as the [Policy Enforcement Point (PEP)](https://csrc.nist.gov/glossary/term/policy_enforcement_point).
 
-Furthermore, the OpenTDF platform is designed for flexibility. Developers can **build and integrate their own custom PEPs**. These custom enforcement points can leverage the platform's robust Authorization (PDP) and Policy (PAP) services while implementing enforcement logic tailored to specific applications. These custom PEPs can also optionally interface with the KAS to take advantage of its powerful cryptographic capabilities.
+Furthermore, the OpenTDF platform is designed for flexibility. Developers can **build and integrate their own custom PEPs**. These custom enforcement points can leverage the platform's robust Authorization ([PDP](https://csrc.nist.grov/glossary/term/policy_decision_point)) and Policy ([PAP](https://csrc.nist.gov/glossary/term/policy_administration_point)) services while implementing enforcement logic tailored to specific applications. These custom PEPs can also optionally interface with the KAS to take advantage of its powerful cryptographic capabilities.