docs: Make the spelling of "modelling" consistent (#4039)

Author: eandersons

…ry-tutorial/01-modeling-and-features.rst …y-tutorial/01-modelling-and-features.rstdocs/tutorials/repository-tutorial/01-modeling-and-features.rst renamed to docs/tutorials/repository-tutorial/01-modelling-and-features.rst docs/tutorials/repository-tutorial/01-modeling-and-features.rst renamed to docs/tutorials/repository-tutorial/01-modelling-and-features.rst

@@ -1,14 +1,14 @@
-Introduction to Database Modeling and Repository Features
----------------------------------------------------------
+Introduction to Database Modelling and Repository Features
+----------------------------------------------------------
 In this tutorial, we will cover the integrated repository features in Litestar, starting
-with database modeling using the included SQLAlchemy declarative model helpers. These
+with database modelling using the included SQLAlchemy declarative model helpers. These
 are a series of classes and mixins that incorporate commonly used functions/column types
 to make working with models easier.
 
 .. tip:: The full code for this tutorial can be found below in the :ref:`Full Code <01-repo-full-code>` section.
 
-Modeling
---------
+Modelling
+---------
 
 We'll begin by modelling the entities and relationships between authors and books.
 We'll start by creating the ``Author`` table, utilizing the

docs/tutorials/repository-tutorial/02-repository-introduction.rst

@@ -1,6 +1,6 @@
 Interacting with repositories
 -----------------------------
-Now that we've covered the modeling basics, we are able to create our first repository
+Now that we've covered the modelling basics, we are able to create our first repository
 class.  The repository classes include all of the standard CRUD operations as well as a
 few advanced features such as pagination, filtering and bulk operations.
 

docs/tutorials/repository-tutorial/index.rst

@@ -17,7 +17,7 @@ databases a breeze. Lets get started!
 .. toctree::
     :hidden:
 
-    01-modeling-and-features
+    01-modelling-and-features
     02-repository-introduction
     03-repository-controller
     04-repository-other

litestar/app.py

@@ -309,8 +309,8 @@ def __init__(
             security: A sequence of dicts that will be added to the schema of all route handlers in the application.
                 See
                 :data:`SecurityRequirement <.openapi.spec.SecurityRequirement>` for details.
-            signature_namespace: A mapping of names to types for use in forward reference resolution during signature modeling.
-            signature_types: A sequence of types for use in forward reference resolution during signature modeling.
+            signature_namespace: A mapping of names to types for use in forward reference resolution during signature modelling.
+            signature_types: A sequence of types for use in forward reference resolution during signature modelling.
                 These types will be added to the signature namespace using their ``__name__`` attribute.
             state: An optional :class:`State <.datastructures.State>` for application state.
             static_files_config: A sequence of :class:`StaticFilesConfig <.static_files.StaticFilesConfig>`

litestar/config/app.py

@@ -193,9 +193,9 @@ class AppConfig:
     :data:`SecurityRequirement <.openapi.spec.SecurityRequirement>` for details.
     """
     signature_namespace: dict[str, Any] = field(default_factory=dict)
-    """A mapping of names to types for use in forward reference resolution during signature modeling."""
+    """A mapping of names to types for use in forward reference resolution during signature modelling."""
     signature_types: list[Any] = field(default_factory=list)
-    """A sequence of types for use in forward reference resolution during signature modeling.
+    """A sequence of types for use in forward reference resolution during signature modelling.
 
     These types will be added to the signature namespace using their ``__name__`` attribute.
     """

litestar/controller.py

@@ -159,9 +159,9 @@ class Controller:
     security: Sequence[SecurityRequirement] | None
     """A sequence of dictionaries that to the schema of all route handlers under the controller."""
     signature_namespace: dict[str, Any]
-    """A mapping of names to types for use in forward reference resolution during signature modeling."""
+    """A mapping of names to types for use in forward reference resolution during signature modelling."""
     signature_types: Sequence[Any]
-    """A sequence of types for use in forward reference resolution during signature modeling.
+    """A sequence of types for use in forward reference resolution during signature modelling.
 
     These types will be added to the signature namespace using their ``__name__`` attribute.
     """

litestar/handlers/base.py

@@ -113,7 +113,7 @@ def __init__(
                 outbound response data.
             signature_namespace: A mapping of names to types for use in forward reference resolution during signature
                 modelling.
-            signature_types: A sequence of types for use in forward reference resolution during signature modeling.
+            signature_types: A sequence of types for use in forward reference resolution during signature modelling.
                 These types will be added to the signature namespace using their ``__name__`` attribute.
             type_decoders: A sequence of tuples, each composed of a predicate testing for type identity and a msgspec hook for deserialization.
             type_encoders: A mapping of types to callables that transform them into types supported for serialization.

litestar/router.py

@@ -160,8 +160,8 @@ def __init__(
             security: A sequence of dicts that will be added to the schema of all route handlers in the application.
                 See :data:`SecurityRequirement <.openapi.spec.SecurityRequirement>`
                 for details.
-            signature_namespace: A mapping of names to types for use in forward reference resolution during signature modeling.
-            signature_types: A sequence of types for use in forward reference resolution during signature modeling.
+            signature_namespace: A mapping of names to types for use in forward reference resolution during signature modelling.
+            signature_types: A sequence of types for use in forward reference resolution during signature modelling.
                 These types will be added to the signature namespace using their ``__name__`` attribute.
             tags: A sequence of string tags that will be appended to the schema of all route handlers under the
                 application.

litestar/testing/helpers.py

@@ -222,8 +222,8 @@ def test_my_handler() -> None:
         security: A sequence of dicts that will be added to the schema of all route handlers in the application.
             See
             :data:`SecurityRequirement <.openapi.spec.SecurityRequirement>` for details.
-        signature_namespace: A mapping of names to types for use in forward reference resolution during signature modeling.
-        signature_types: A sequence of types for use in forward reference resolution during signature modeling.
+        signature_namespace: A mapping of names to types for use in forward reference resolution during signature modelling.
+        signature_types: A sequence of types for use in forward reference resolution during signature modelling.
             These types will be added to the signature namespace using their ``__name__`` attribute.
         state: An optional :class:`State <.datastructures.State>` for application state.
         static_files_config: A sequence of :class:`StaticFilesConfig <.static_files.StaticFilesConfig>`
@@ -483,8 +483,8 @@ async def test_my_handler() -> None:
         security: A sequence of dicts that will be added to the schema of all route handlers in the application.
             See
             :data:`SecurityRequirement <.openapi.spec.SecurityRequirement>` for details.
-        signature_namespace: A mapping of names to types for use in forward reference resolution during signature modeling.
-        signature_types: A sequence of types for use in forward reference resolution during signature modeling.
+        signature_namespace: A mapping of names to types for use in forward reference resolution during signature modelling.
+        signature_types: A sequence of types for use in forward reference resolution during signature modelling.
             These types will be added to the signature namespace using their ``__name__`` attribute.
         state: An optional :class:`State <.datastructures.State>` for application state.
         static_files_config: A sequence of :class:`StaticFilesConfig <.static_files.StaticFilesConfig>`