refactor: Change yaml-file to YAML-file for all versions for consiste…

…ncy.

docs/06-concepts/04-exceptions.md

@@ -12,7 +12,7 @@ Use the Serverpod Insights app to view your logs. It will show any failed or slo
 
 ## Serializable exceptions
 
-Serverpod allows adding data to an exception you throw on the server and extracting that data in the client. This is useful for passing error messages back to the client when a call fails. You use the same yaml-files to define the serializable exceptions as you would with any serializable model (see [serialization](serialization) for details). The only difference is that you use the keyword `exception` instead of `class`.
+Serverpod allows adding data to an exception you throw on the server and extracting that data in the client. This is useful for passing error messages back to the client when a call fails. You use the same YAML-files to define the serializable exceptions as you would with any serializable model (see [serialization](serialization) for details). The only difference is that you use the keyword `exception` instead of `class`.
 
 ```yaml
 exception: MyException

docs/06-concepts/06-database/04-indexing.md

@@ -1,10 +1,10 @@
 # Indexing
 
-For performance reasons, you may want to add indexes to your database tables. These are added in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. These are added in the YAML-files defining the serializable objects.
 
 ### Add an index
 
-To add an index, add an `indexes` section to the yaml-file. The `indexes` section is a map where the key is the name of the index and the value is a map with the index details.
+To add an index, add an `indexes` section to the YAML-file. The `indexes` section is a map where the key is the name of the index and the value is a map with the index details.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.10/03-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.10/03-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.11/03-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.11/03-concepts/03-database-communication.md

@@ -33,7 +33,7 @@ If you use the `database` or `api` options the field must be nullable.
 :::
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.20/04-concepts/02-serialization.md

@@ -2,9 +2,9 @@
 Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database.
 
 ## Serverpod's native serialization
-The structure for your serialized classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+The structure for your serialized classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.20/04-concepts/03-database-communication.md

@@ -39,7 +39,7 @@ If you use the `database` or `api` options the field must be nullable.
 :::
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.20/04-concepts/06-modules.md

@@ -57,7 +57,7 @@ dependencies:
 ```
 
 ## Referencing a module
-It can be useful to reference serializable objects in other modules from the yaml-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
+It can be useful to reference serializable objects in other modules from the YAML-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
 
 ```yaml
 class: MyClass
@@ -84,4 +84,4 @@ In your Flutter package, you most likely want to import the client libraries cre
 
 Most modules will need a set of database tables to function. When naming the tables, you should use the module name as a prefix to the table name to avoid any conflicts. For instance, the Serverpod tables are prefixed with `serverpod_`.
 
-:::
+:::

versioned_docs/version-0.9.21/04-concepts/02-serialization.md

@@ -2,9 +2,9 @@
 Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database.
 
 ## Serverpod's native serialization
-The structure for your serialized classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+The structure for your serialized classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.21/04-concepts/03-database-communication.md

@@ -39,7 +39,7 @@ If you use the `database` or `api` options the field must be nullable.
 :::
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.21/04-concepts/06-modules.md

@@ -57,7 +57,7 @@ dependencies:
 ```
 
 ## Referencing a module
-It can be useful to reference serializable objects in other modules from the yaml-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
+It can be useful to reference serializable objects in other modules from the YAML-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
 
 ```yaml
 class: MyClass
@@ -84,4 +84,4 @@ In your Flutter package, you most likely want to import the client libraries cre
 
 Most modules will need a set of database tables to function. When naming the tables, you should use the module name as a prefix to the table name to avoid any conflicts. For instance, the Serverpod tables are prefixed with `serverpod_`.
 
-:::
+:::

versioned_docs/version-0.9.22/04-concepts/02-serialization.md

@@ -2,9 +2,9 @@
 Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database.
 
 ## Serverpod's native serialization
-The structure for your serialized classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+The structure for your serialized classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.22/04-concepts/03-database-communication.md

@@ -39,7 +39,7 @@ If you use the `database` or `api` options the field must be nullable.
 :::
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.22/04-concepts/06-modules.md

@@ -57,7 +57,7 @@ dependencies:
 ```
 
 ## Referencing a module
-It can be useful to reference serializable objects in other modules from the yaml-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
+It can be useful to reference serializable objects in other modules from the YAML-files in your protocol directory. You do this by adding the module prefix, followed by the nickname of the package. For instance, this is how you reference a serializable class in the auth package.
 
 ```yaml
 class: MyClass
@@ -84,4 +84,4 @@ In your Flutter package, you most likely want to import the client libraries cre
 
 Most modules will need a set of database tables to function. When naming the tables, you should use the module name as a prefix to the table name to avoid any conflicts. For instance, the Serverpod tables are prefixed with `serverpod_`.
 
-:::
+:::

versioned_docs/version-0.9.5/02-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.5/02-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.6/02-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.6/02-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.7/03-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.7/03-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.8/03-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.8/03-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-0.9.9/03-concepts/02-serialization.md

@@ -1,7 +1,7 @@
 # Serialization
-Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database. The structure for the classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-0.9.9/03-concepts/03-database-communication.md

@@ -27,7 +27,7 @@ fields:
 Likewise, if you only want a field to be accessible in the protocol but not stored in the server, you can add the `api` flag. By default, a field is accessible to both the API and the database.
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company

versioned_docs/version-1.0.0/04-concepts/02-serialization.md

@@ -2,9 +2,9 @@
 Serverpod makes it easy to generate serializable classes that can be passed between server and client or used to communicate with the database.
 
 ## Serverpod's native serialization
-The structure for your serialized classes is defined in yaml-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
+The structure for your serialized classes is defined in YAML-files in the `protocol` directory. Run `serverpod generate` to build the Dart code for the classes and make them accessible to both the server and client.
 
-Here is a simple example of a yaml-file defining a serializable class:
+Here is a simple example of a YAML-file defining a serializable class:
 
 ```yaml
 class: Company

versioned_docs/version-1.0.0/04-concepts/03-database-communication.md

@@ -39,7 +39,7 @@ If you use the `database` or `api` options the field must be nullable.
 :::
 
 ### Database indexes
-For performance reasons, you may want to add indexes to your database tables. You add these in the yaml-files defining the serializable objects.
+For performance reasons, you may want to add indexes to your database tables. You add these in the YAML-files defining the serializable objects.
 
 ```yaml
 class: Company