Update headersToPropagate property in af-project-files.adoc to use a multi-line format for MCP server and agent configurations, enhancing clarity and consistency in documentation.

Author: IsaacEldridge

modules/ROOT/pages/af-project-files.adoc

@@ -342,7 +342,9 @@ tools:
         name: talent-pool-mcp         # Exchange asset ID of MCP server. By default, the groupId for this asset is the same as that in exchange.json.
       allowed:                        # Allowlist specific tools
         - TalentPoolMcpServer.match_email_to_address
-      headersToPropagate: [Authorization, X-Request-Id]           # Optional. Header names to forward when invoking this tool.
+      headersToPropagate: 
+        - Authorization
+        - X-Correlation-Id           # Optional. Header names to forward when invoking this tool.
   - mcp:
       ref:
         name: slack-mcp
@@ -378,7 +380,9 @@ links:
       ref:
         name: hr-agent        # Exchange asset ID of the linked agent. By default, the groupId for this asset is the same as that in exchange.json.
         namespace:            # Optional. If the asset was defined in a different business group, set the corresponding groupId here.
-      headersToPropagate: [Authorization, X-Request-Id]   # Optional. Header names to forward when invoking this agent.
+      headersToPropagate: 
+        - Authorization
+        - X-Correlation-Id   # Optional. Header names to forward when invoking this agent.
   - agent:
       ref:
         name: badging-agent
@@ -418,7 +422,7 @@ The `links` element has these properties.
 |`links[].agent.ref.name` |Exchange asset ID of the linked agent. This references the `assetId` that the agent has in Anypoint Exchange, not the human-friendly name.|String|Asset ID string (for example, "hr-agent", "crm-agent"). By default, the groupId for this asset is the same as that in exchange.json|Yes
 |`links[].agent.ref.namespace` |Business group ID (groupId) where the asset is defined. Use this when the asset was defined in a different business group than the current one.|String|Group ID string. To find the groupId, look in the `dependencies` section in `exchange.json`|No
 |`links[].agent.connection.ref` |Connection reference.|String|See <<connections-section,Connections>>. This references a connection defined in the `connections` section|No
-|`links[].agent.headersToPropagate` |The names of the request headers to propagate when the broker invokes this agent.|Array of strings|Array of header name strings (for example, `X-Request-Id`, `Authorization`)|No
+|`links[].agent.headersToPropagate` |The names of the request headers to propagate when the broker invokes this agent.|Array of strings|Array of header name strings |No
 |===