Fix incorrect casing in documentation

Author: bkoelman

docs/usage/extensibility/services.md

@@ -140,7 +140,7 @@ Then on your model, pass in the set of endpoints to expose (the ones that you've
 ```c#
 [Resource(GenerateControllerEndpoints =
     JsonApiEndpoints.Create | JsonApiEndpoints.Delete)]
-public class Article : identifiable<long>
+public class Article : Identifiable<long>
 {
     // ...
 }

docs/usage/options.md

@@ -137,7 +137,7 @@ options.ValidateModelState = true;
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr]
     [MinLength(3)]

docs/usage/resource-graph.md

@@ -73,15 +73,15 @@ builder.Services.AddJsonApi(resources: resourceGraphBuilder =>
 2. The `PublicName` property when a model is decorated with a `ResourceAttribute`.
 ```c#
 [Resource(PublicName = "individuals")]
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
 }
 ```
 
 3. The configured naming convention (by default this is camel-case), after pluralization.
 ```c#
 // this will be registered as "people"
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
 }
 ```

docs/usage/resources/attributes.md

@@ -5,7 +5,7 @@ If you want an attribute on your model to be publicly available, add the `AttrAt
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr]
     public string? FirstName { get; set; }
@@ -24,7 +24,7 @@ There are two ways the exposed attribute name is determined:
 2. Individually using the attribute's constructor.
 ```c#
 #nullable enable
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr(PublicName = "first-name")]
     public string? FirstName { get; set; }
@@ -51,7 +51,7 @@ Otherwise, the attribute is silently omitted.
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [Attr(Capabilities = ~AttrCapabilities.AllowView)]
     public string Password { get; set; } = null!;
@@ -65,7 +65,7 @@ Indicates whether the attribute can be filtered on. When not allowed and used in
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr(Capabilities = AttrCapabilities.AllowFilter)]
     public string? FirstName { get; set; }
@@ -79,7 +79,7 @@ Indicates whether the attribute can be sorted on. When not allowed and used in `
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr(Capabilities = ~AttrCapabilities.AllowSort)]
     public string? FirstName { get; set; }
@@ -93,7 +93,7 @@ Indicates whether POST requests can assign the attribute value. When sent but no
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr(Capabilities = AttrCapabilities.AllowCreate)]
     public string? CreatorName { get; set; }
@@ -107,7 +107,7 @@ Indicates whether PATCH requests can update the attribute value. When sent but n
 ```c#
 #nullable enable
 
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Attr(Capabilities = AttrCapabilities.AllowChange)]
     public string? FirstName { get; set; };
@@ -124,7 +124,7 @@ You can also use [global options](~/usage/options.md#customize-serializer-option
 ```c#
 #nullable enable
 
-public class Foo : identifiable<long>
+public class Foo : Identifiable<long>
 {
     [Attr]
     public Bar? Bar { get; set; }
@@ -146,7 +146,7 @@ and retrieval.
 ```c#
 #nullable enable
 
-public class Foo : identifiable<long>
+public class Foo : Identifiable<long>
 {
     [Attr]
     [NotMapped]

docs/usage/resources/index.md

@@ -14,7 +14,7 @@ public class Person : Identifiable<Guid>
 If you need to attach annotations or attributes on the `Id` property, you can override the virtual property.
 
 ```c#
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [Key]
     [Column("PersonID")]

docs/usage/resources/nullability.md

@@ -12,7 +12,7 @@ To make JsonApiDotNetCore return an error when such a property is missing on res
 Example:
 
 ```c#
-public sealed class User : identifiable<long>
+public sealed class User : Identifiable<long>
 {
     [Attr]
     [Required]
@@ -35,7 +35,7 @@ Example:
 ```c#
 #nullable disable
 
-public sealed class Label : identifiable<long>
+public sealed class Label : Identifiable<long>
 {
     [Attr]
     [Required]
@@ -69,7 +69,7 @@ Example:
 ```c#
 #nullable enable
 
-public sealed class Label : identifiable<long>
+public sealed class Label : Identifiable<long>
 {
     [Attr]
     public string Name { get; set; } = null!;

docs/usage/resources/relationships.md

@@ -13,7 +13,7 @@ This exposes a to-one relationship.
 ```c#
 #nullable enable
 
-public class TodoItem : identifiable<long>
+public class TodoItem : Identifiable<long>
 {
     [HasOne]
     public Person? Owner { get; set; }
@@ -36,13 +36,13 @@ The next example defines that each car requires an engine, while an engine is op
 ```c#
 #nullable enable
 
-public sealed class Car : identifiable<long>
+public sealed class Car : Identifiable<long>
 {
     [HasOne]
     public Engine Engine { get; set; } = null!;
 }
 
-public sealed class Engine : identifiable<long>
+public sealed class Engine : Identifiable<long>
 {
     [HasOne]
     public Car? Car { get; set; }
@@ -123,13 +123,13 @@ The next example defines that each car optionally has an engine, while an engine
 ```c#
 #nullable enable
 
-public sealed class Car : identifiable<long>
+public sealed class Car : Identifiable<long>
 {
     [HasOne]
     public Engine? Engine { get; set; }
 }
 
-public sealed class Engine : identifiable<long>
+public sealed class Engine : Identifiable<long>
 {
     [HasOne]
     public Car? Car { get; set; }
@@ -204,7 +204,7 @@ CREATE UNIQUE INDEX "IX_Cars_EngineId" ON "Cars" ("EngineId");
 This exposes a to-many relationship.
 
 ```c#
-public class Person : identifiable<long>
+public class Person : Identifiable<long>
 {
     [HasMany]
     public ICollection<TodoItem> TodoItems { get; set; } = new HashSet<TodoItem>();
@@ -236,7 +236,7 @@ However, under the covers it would use the join type and Entity Framework Core's
 ```c#
 #nullable disable
 
-public class Article : identifiable<long>
+public class Article : Identifiable<long>
 {
     // tells Entity Framework Core to ignore this property
     [NotMapped]
@@ -261,7 +261,7 @@ There are two ways the exposed relationship name is determined:
 2. Individually using the attribute's constructor.
 ```c#
 #nullable enable
-public class TodoItem : identifiable<long>
+public class TodoItem : Identifiable<long>
 {
     [HasOne(PublicName = "item-owner")]
     public Person Owner { get; set; } = null!;
@@ -294,7 +294,7 @@ Otherwise, the relationship (and its related resources, when included) are silen
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasOne(Capabilities = ~HasOneCapabilities.AllowView)]
     public LoginAccount Account { get; set; } = null!;
@@ -308,7 +308,7 @@ Indicates whether the relationship can be included. When not allowed and used in
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasMany(Capabilities = ~HasManyCapabilities.AllowInclude)]
     public ISet<Group> Groups { get; set; } = new HashSet<Group>();
@@ -322,7 +322,7 @@ For to-many relationships only. Indicates whether it can be used in the `count()
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasMany(Capabilities = HasManyCapabilities.AllowFilter)]
     public ISet<Group> Groups { get; set; } = new HashSet<Group>();
@@ -336,7 +336,7 @@ Indicates whether POST and PATCH requests can replace the relationship. When sen
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasOne(Capabilities = ~HasOneCapabilities.AllowSet)]
     public LoginAccount Account { get; set; } = null!;
@@ -350,7 +350,7 @@ For to-many relationships only. Indicates whether POST requests can add resource
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasMany(Capabilities = ~HasManyCapabilities.AllowAdd)]
     public ISet<Group> Groups { get; set; } = new HashSet<Group>();
@@ -364,7 +364,7 @@ For to-many relationships only. Indicates whether DELETE requests can remove res
 ```c#
 #nullable enable
 
-public class User : identifiable<long>
+public class User : Identifiable<long>
 {
     [HasMany(Capabilities = ~HasManyCapabilities.AllowRemove)]
     public ISet<Group> Groups { get; set; } = new HashSet<Group>();
@@ -380,7 +380,7 @@ Relationships can be marked to disallow including them using the `?include=` que
 ```c#
 #nullable enable
 
-public class TodoItem : identifiable<long>
+public class TodoItem : Identifiable<long>
 {
     [HasOne(CanInclude: false)]
     public Person? Owner { get; set; }
@@ -397,7 +397,7 @@ So for the calculated property to be evaluated correctly, the related entity mus
 ```c#
 #nullable enable
 
-public class ShippingAddress : identifiable<long>
+public class ShippingAddress : Identifiable<long>
 {
     [Attr]
     public string Street { get; set; } = null!;

docs/usage/routing.md

@@ -23,7 +23,7 @@ The library will configure routes for all auto-generated and hand-written contro
 ```c#
 // Auto-generated
 [Resource]
-public class OrderSummary : identifiable<long>
+public class OrderSummary : Identifiable<long>
 {
 }