fix: links

Author: DaveOrDead

src/content/docs/machine-to-machine-applications/m2m-application-setup/add-metadata-to-an-m2m-application-with-properties.mdx

@@ -17,7 +17,7 @@ This is useful for:
 - Driving logic in downstream systems
 - Managing AI agent behavior
 
-If you're looking to include properties inside tokens, see [Customize the contents of an M2M token](/machine-to-machine-applications/m2m-application-setup/m2m-token-customization/).
+If you're looking to include properties inside tokens, see [Customize the claims of an M2M token with properties](/machine-to-machine-applications/m2m-application-setup/add-metadata-to-an-m2m-application-with-properties/).
 
 ## Step 1 - Define your property
 

src/content/docs/machine-to-machine-applications/m2m-token-customization/customize-m2m-tokens.mdx

@@ -12,6 +12,7 @@ relatedArticles:
 You can customize the claims of tokens issued to Machine-to-Machine (M2M) applications in Kinde by including selected **Properties** and **Feature Flags**. This allows you to inject structured metadata and configuration directly into the token, without requiring an additional lookup at runtime.
 
 This is useful for:
+
 - Routing or behavior changes based on metadata
 - Feature gating in backend systems
 - Configuring AI agents or other automation tools
@@ -22,6 +23,7 @@ This is useful for:
 2. Select the **Tokens** tab
 
 From here you can:
+
 - Set the token lifetime
 - Enable **Hasura-compatible mapping**
 - Opt to include scopes under a `permissions` claim
@@ -42,7 +44,7 @@ The value will appear in the token under a `application_properties` claim:
 
 ```json
 {
-"application_properties": {
+  "application_properties": {
     "region": {
       "v": "eu"
     },
@@ -71,17 +73,18 @@ Example:
 ```json
 {
   "feature_flags": {
-      "new-ai-agent": {
-          "t": "b",
-          "v": true
-       },
-  	   "access-level": {
-          "t": "s",
-          "v": "beta"
-       }
+    "new-ai-agent": {
+      "t": "b",
+      "v": true
+    },
+    "access-level": {
+      "t": "s",
+      "v": "beta"
     }
+  }
 }
 ```
+
 The `t` and `v` are short codes for the type and value of the feature flag.
 
 - `t` = `type` (boolean, string, number)
@@ -100,7 +103,7 @@ Only the feature flags you explicitly toggle on will be included.
 For complete control over the token, you can use the [Kinde M2M token generation workflow](/machine-to-machine-applications/m2m-workflow-automation/m2m-workflow/) to customize the token further.
 
 For example, you can:
+
 - Add custom claims to the token
 - Add custom scopes to the token
 - Add custom metadata to the token
-