Fix fat-finger incidents

hsnabszhdn · hsnabszhdn · commit 9a20b5bceb4d · 2025-07-04T13:02:10.000+10:00
diff --git a/docs/specs/devcontainer-features.md b/docs/specs/devcontainer-features.md
@@ -355,11 +355,11 @@ If a Feature is indicated in `overrideFeatureInstallOrder` but not a member of t
 > ## Definitions
 > ### Definition: Feature Equality
 >
-> This specification defines two Features as equal if both Features point to the same exact contents and are executed with > the same options.
+> This specification defines two Features as equal if both Features point to the same exact contents and are executed with the same options.
 > 
-> **For Features published to an OCI registry**, two Feature are identical if their manifest digests are equal, and the > options executed against the Feature are equal (compared value by value).  Identical manifest digests implies that the tgz  contents of the Feature and its entire `devcontainer-feature.json` are identical.  If any of these conditions are not met,  the Features are considered not equal.
+> **For Features published to an OCI registry**, two Feature are identical if their manifest digests are equal, and the options executed against the Feature are equal (compared value by value).  Identical manifest digests implies that the tgz  contents of the Feature and its entire `devcontainer-feature.json` are identical.  If any of these conditions are not met,  the Features are considered not equal.
 > 
-> **For Features fetched by HTTPS URI**, two Features are identical if the contents of the tgz are identical (hash to the > same value), and the options executed against the Feature are equal (compared value by value).  If any of these conditions  are not met, the Features are considered not equal.
+> **For Features fetched by HTTPS URI**, two Features are identical if the contents of the tgz are identical (hash to the same value), and the options executed against the Feature are equal (compared value by value).  If any of these conditions  are not met, the Features are considered not equal.
 > 
 > **For local Features**, each Feature is considered unique and not equal to any other local Feature.
 > 
@@ -394,7 +394,7 @@ If a Feature is indicated in `overrideFeatureInstallOrder` but not a member of t
 > 
 > Each node in the graph has an implicit, default `roundPriority` of 0.
 > 
-> To influence installation order globally while still honoring the dependency graph of built in **(1)**, `roundPriority` values may be tweaks for each Feature.  When each round is calculated in **(3)**, only the Features equal to the max `roundPriority` of that set will be committed (the remaining will be > uncommitted and reevaulated in subsequent rounds).
+> To influence installation order globally while still honoring the dependency graph of built in **(1)**, `roundPriority` values may be tweaks for each Feature.  When each round is calculated in **(3)**, only the Features equal to the max `roundPriority` of that set will be committed (the remaining will be uncommitted and reevaulated in subsequent rounds).
 > 
 > The `roundPriority` is set to a non-zero value in the following instances:
 > 

Original file line number	Diff line number	Diff line change
@@ -355,11 +355,11 @@ If a Feature is indicated in `overrideFeatureInstallOrder` but not a member of t
`355`	`355`	`> ## Definitions`
`356`	`356`	`> ### Definition: Feature Equality`
`357`	`357`	`>`
`358`		`-> This specification defines two Features as equal if both Features point to the same exact contents and are executed with > the same options.`
	`358`	`+> This specification defines two Features as equal if both Features point to the same exact contents and are executed with the same options.`
`359`	`359`	`>`
`360`		-> For Features published to an OCI registry, two Feature are identical if their manifest digests are equal, and the > options executed against the Feature are equal (compared value by value). Identical manifest digests implies that the tgz contents of the Feature and its entire `devcontainer-feature.json` are identical. If any of these conditions are not met, the Features are considered not equal.
	`360`	+> For Features published to an OCI registry, two Feature are identical if their manifest digests are equal, and the options executed against the Feature are equal (compared value by value). Identical manifest digests implies that the tgz contents of the Feature and its entire `devcontainer-feature.json` are identical. If any of these conditions are not met, the Features are considered not equal.
`361`	`361`	`>`
`362`		`-> For Features fetched by HTTPS URI, two Features are identical if the contents of the tgz are identical (hash to the > same value), and the options executed against the Feature are equal (compared value by value). If any of these conditions are not met, the Features are considered not equal.`
	`362`	`+> For Features fetched by HTTPS URI, two Features are identical if the contents of the tgz are identical (hash to the same value), and the options executed against the Feature are equal (compared value by value). If any of these conditions are not met, the Features are considered not equal.`
`363`	`363`	`>`
`364`	`364`	`> For local Features, each Feature is considered unique and not equal to any other local Feature.`
`365`	`365`	`>`
@@ -394,7 +394,7 @@ If a Feature is indicated in `overrideFeatureInstallOrder` but not a member of t
`394`	`394`	`>`
`395`	`395`	> Each node in the graph has an implicit, default `roundPriority` of 0.
`396`	`396`	`>`
`397`		-> To influence installation order globally while still honoring the dependency graph of built in (1), `roundPriority` values may be tweaks for each Feature. When each round is calculated in (3), only the Features equal to the max `roundPriority` of that set will be committed (the remaining will be > uncommitted and reevaulated in subsequent rounds).
	`397`	+> To influence installation order globally while still honoring the dependency graph of built in (1), `roundPriority` values may be tweaks for each Feature. When each round is calculated in (3), only the Features equal to the max `roundPriority` of that set will be committed (the remaining will be uncommitted and reevaulated in subsequent rounds).
`398`	`398`	`>`
`399`	`399`	> The `roundPriority` is set to a non-zero value in the following instances:
`400`	`400`	`>`