Merge pull request #24 from flaksp/main

Fix typo in "Using Dynamic References to Support Generic Types"

Author: gregsdennis

pages/posts/dynamicref-and-generics.md

@@ -112,7 +112,7 @@ You can also use multiple dynamic anchors to support types like `Dictionary<TKey
     "type": "object",
     "properties": {
       "key": { "$dynamicRef": "#TKey" },
-      "key": { "$dynamicRef": "#TValue" }
+      "value": { "$dynamicRef": "#TValue" }
     }
   }
 }
@@ -169,4 +169,4 @@ By using `$dynamicRef` and `$dynamicAnchor`, you don't need to write full schema
 _**ASIDE** With Draft 2020-12, including `$dynamicAnchor` in the generic schema is required for `$dynamicRef` to work.  In future versions, this requirement will be removed as it isn't strictly needed: any resolution attempt will simply fail.  (This requirement is a holdover from its Draft 2019-09 predecessor `$recursive*`.)  However for the particular application of modelling generic types, I'd still keep it in because it serves as an analog for not being able to instantiate a generic type, like `List<T>`.  The net outcome is the same (validation failure), but I think including it more explicitly describes the intent._
 
 
-_Cover photo by [Nick Fewings](https://unsplash.com/@jannerboy62) on [Unsplash](https://unsplash.com/photos/-sAtFFj28W4) with some edits by me._ 😁
+_Cover photo by [Nick Fewings](https://unsplash.com/@jannerboy62) on [Unsplash](https://unsplash.com/photos/-sAtFFj28W4) with some edits by me._ 😁