metadata docs

Author: siddharthsambharia-portkey

product/administration/enforcing-request-metadata.mdx

@@ -152,7 +152,7 @@ When creating a new workspace, you must provide metadata that conforms to the de
 
 
 
-## Metadata Precedence
+## Metadata Precedence Order
 
 When the same key appears at multiple levels, the **precedence order** is:
 
@@ -176,13 +176,3 @@ Best Practices
 
 ## Support
 For questions about configuring metadata schemas or troubleshooting issues, contact [Portkey support](mailto:[email protected]) or reach out on [Discord](https://portkey.sh/reddit-discord).
-
-## Metadata Precedence Order
-
-When identical metadata keys are passed at different levels (workspace settings, API key settings, or request level), Portkey follows this precedence order:
-
-1. **Incoming request metadata** (highest priority)
-2. **API key metadata**
-3. **Workspace metadata** (lowest priority)
-
-This means that if the same key exists at multiple levels, the value from the incoming request will take precedence over the API key's metadata, which in turn will override any workspace-level metadata setting for that key.