Apply suggestions from code review

peppelinux · selfissued · web-flow · commit 903e772f3803 · 2024-10-02T16:06:16.000+02:00
Co-authored-by: Michael B. Jones &lt;michael_b_jones@hotmail.com&gt;
diff --git a/openid-federation-wallet-1_0.md b/openid-federation-wallet-1_0.md
@@ -421,7 +421,6 @@ These modifications allow a federation authority, such as a Trust Anchor, to app
 
 The key difference between `metadata` and `metadata_policy` is that metadata directly affects only the Immediate Subordinate Entity, while `metadata_policy` impacts the configuration of all Subordinate Entities along a Trust Chain, as defined in Sections 5 and 6.1 of [@!OpenID.Federation].
 
-The `metadata` parameter allows federation authorities managing Immediate Subordinates' registrations to sanitize their configurations in an arbitrary way, without necessarily using the policy language in the `metadata_policy` parameter. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration and finalize it by setting specific metadata parameters. The `metadata` parameter value updates all the matching parts of the `metadata` JSON object contained within the Subordinate Entity Configuration.
 
 ## Using Metadata Policies
 

Original file line number	Diff line number	Diff line change
`@@ -421,7 +421,6 @@ These modifications allow a federation authority, such as a Trust Anchor, to app`
`421`	`421`
`422`	`422`	The key difference between `metadata` and `metadata_policy` is that metadata directly affects only the Immediate Subordinate Entity, while `metadata_policy` impacts the configuration of all Subordinate Entities along a Trust Chain, as defined in Sections 5 and 6.1 of [@!OpenID.Federation].
`423`	`423`
`424`		-The `metadata` parameter allows federation authorities managing Immediate Subordinates' registrations to sanitize their configurations in an arbitrary way, without necessarily using the policy language in the `metadata_policy` parameter. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration and finalize it by setting specific metadata parameters. The `metadata` parameter value updates all the matching parts of the `metadata` JSON object contained within the Subordinate Entity Configuration.
`425`	`424`
`426`	`425`	`## Using Metadata Policies`
`427`	`426`