add warnings about AOT in examples; update examples

Author: gregsdennis

_docs/schema/codegen/mini-meta-schemas.md

@@ -5,6 +5,12 @@ permalink: /schema/codegen/:title/
 icon: fas fa-tag
 order: "01.6.3"
 ---
+> **DEPRECATION NOTICE**
+>
+> *JsonSchema.Net.CodeGeneration* is no longer being developed.
+> 
+> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
+{: .prompt-danger }
 
 This page serves as a reference to the mini-meta-schemas that are used to identify the supported patterns.
 

_docs/schema/codegen/patterns.md

@@ -5,6 +5,12 @@ permalink: /schema/codegen/:title/
 icon: fas fa-tag
 order: "01.6.2"
 ---
+> **DEPRECATION NOTICE**
+>
+> *JsonSchema.Net.CodeGeneration* is no longer being developed.
+> 
+> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
+{: .prompt-danger }
 
 This page gives more technical information on the various schema patterns that are supported by the code generation functionality.
 

_docs/schema/codegen/schema-codegen.md

@@ -6,6 +6,13 @@ permalink: /schema/codegen/:title/
 icon: fas fa-tag
 order: "01.6.1"
 ---
+> **DEPRECATION NOTICE**
+>
+> *JsonSchema.Net.CodeGeneration* is no longer being developed.
+> 
+> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
+{: .prompt-danger }
+
 *JsonSchema.Net.CodeGeneration* is a tool that can create C# code from JSON Schemas.
 
 For example, given the schema:

_docs/schema/examples/custom-vocabs.md

@@ -75,7 +75,6 @@ class MaxDateJsonConverter : JsonConverter<MaxDateKeyword>
                                MaxDateKeyword value,
                                JsonSerializerOptions options)
     {
-        writer.WritePropertyName(MaxDateKeyword.Name);
         writer.WriteStringValue(value.Date.ToString("yyyy'-'MM'-'dd'T'HH':'mm':'ssK"));
     }
 }
@@ -91,9 +90,12 @@ Now that we have the keyword, we need to tell the system about it.
 SchemaKeywordRegistry.Register<MaxDateKeyword>();
 ```
 
-> If you're building a dynamic system where you don't always want the keyword supported, it can be removed using the `SchemaKeywordRegistry.Unregister<T>()` static method.
+> If your app is running in a Native AOT context, you'll need to use the `.Register<MaxDateKeyword>()` overload to properly support serialization.
 {: .prompt-info }
 
+> If you're building a dynamic system where you don't always want the keyword supported, it can be removed using the `SchemaKeywordRegistry.Unregister<T>()` static method.
+{: .prompt-tip }
+
 You'll also want to set the `EvaluationOptions.ProcessCustomKeywords` option to true so that non-dialect keywords are processed.
 
 That's technically all you need to do to support a custom keyword.  However, going forward for JSON Schema, custom keywords should be defined in a custom vocabulary.

_docs/schema/vocabs.md

@@ -132,7 +132,7 @@ Both stages are defined by implementing the single method on `IJsonSchemaKeyword
 
 _JsonSchema.Net_ v6 includes updates to support [Native AOT applications](https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/).  Please be sure to read the main AOT section on the [overview page](/schema/basics#aot).
 
-Frist, you'll need to add `[JsonSerializable]` attributes for any custom keywords.
+First, you'll need to add `[JsonSerializable]` attributes for any custom keywords.
 
 ```c#
 [JsonSerializable(typeof(MyKeyword))]