Fixed #36311 -- Unified spelling of "hardcode" and its variants in docs.

Co-authored-by: Natalia <124304+nessita@users.noreply.github.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt
index fefd8740e7..915c4e9c37 100644
--- a/docs/howto/custom-model-fields.txt
+++ b/docs/howto/custom-model-fields.txt
@@ -432,10 +432,10 @@ that is, when you retrieve data using QuerySet methods like ``get()``,
 Some database column types accept parameters, such as ``CHAR(25)``, where the
 parameter ``25`` represents the maximum column length. In cases like these,
 it's more flexible if the parameter is specified in the model rather than being
-hard-coded in the ``db_type()`` method. For example, it wouldn't make much
-sense to have a ``CharMaxlength25Field``, shown here::
+hardcoded in the ``db_type()`` method. For example, it wouldn't make much sense
+to have a ``CharMaxlength25Field``, shown here::
 
-    # This is a silly example of hard-coded parameters.
+    # This is a silly example of hardcoded parameters.
     class CharMaxlength25Field(models.Field):
         def db_type(self, connection):
             return "char(25)"