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

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

5 files changed, 6 insertions, 6 deletions

diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
index 3722aca2b4..3d0aca9156 100644
--- a/docs/ref/contrib/flatpages.txt
+++ b/docs/ref/contrib/flatpages.txt
@@ -89,7 +89,7 @@ to place the pattern at the end of the other urlpatterns::
     matched.
 
 Another common setup is to use flatpages for a limited set of known pages and
-to hard code their URLs in the :doc:`URLconf </topics/http/urls>`::
+to hardcode their URLs in the :doc:`URLconf </topics/http/urls>`::
 
     from django.contrib.flatpages import views
 
diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt
index d69e4c8e81..f6c39feff7 100644
--- a/docs/ref/contrib/sites.txt
+++ b/docs/ref/contrib/sites.txt
@@ -137,7 +137,7 @@ For example::
             # Do something else.
             pass
 
-It's fragile to hard-code the site IDs like that, in case they change. The
+It's fragile to hardcode the site IDs like that, in case they change. The
 cleaner way of accomplishing the same thing is to check the current site's
 domain::
 
diff --git a/docs/ref/contrib/syndication.txt b/docs/ref/contrib/syndication.txt
index d0a3cc41f7..a81b428d45 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -715,7 +715,7 @@ This example illustrates all possible attributes and methods for a
             Takes an item, as returned by items(), and returns a boolean.
             """
 
-        item_guid_is_permalink = False  # Hard coded value
+        item_guid_is_permalink = False  # Hardcoded value
 
         # ITEM AUTHOR NAME -- One of the following three is optional. The
         # framework looks for them in this order.
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index e15e1c93bf..674626b23f 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -863,7 +863,7 @@ URL, you should define ``get_absolute_url()``.
 
 
 It's good practice to use ``get_absolute_url()`` in templates, instead of
-hard-coding your objects' URLs. For example, this template code is bad:
+hardcoding your objects' URLs. For example, this template code is bad:
 
 .. code-block:: html+django
 
diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt
index f3d967b153..1eb391d8c0 100644
--- a/docs/ref/templates/builtins.txt
+++ b/docs/ref/templates/builtins.txt
@@ -777,7 +777,7 @@ will be displayed if the value has not changed:
 Loads a template and renders it with the current context. This is a way of
 "including" other templates within a template.
 
-The template name can either be a variable or a hard-coded (quoted) string,
+The template name can either be a variable or a hardcoded (quoted) string,
 in either single or double quotes.
 
 This example includes the contents of the template ``"foo/bar.html"``:
@@ -1386,7 +1386,7 @@ given view and optional parameters. Any special characters in the resulting
 path will be encoded using :func:`~django.utils.encoding.iri_to_uri`.
 
 This is a way to output links without violating the DRY principle by having to
-hard-code URLs in your templates:
+hardcode URLs in your templates:
 
 .. code-block:: html+django