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

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

2 files changed, 2 insertions, 2 deletions

diff --git a/docs/intro/tutorial03.txt b/docs/intro/tutorial03.txt
index a19f9c949d..be6251f5f2 100644
--- a/docs/intro/tutorial03.txt
+++ b/docs/intro/tutorial03.txt
@@ -166,7 +166,7 @@ commas, according to publication date:
 
     # Leave the rest of the views (detail, results, vote) unchanged
 
-There's a problem here, though: the page's design is hard-coded in the view. If
+There's a problem here, though: the page's design is hardcoded in the view. If
 you want to change the way the page looks, you'll have to edit this Python code.
 So let's use Django's template system to separate the design from Python by
 creating a template that the view can use.
diff --git a/docs/intro/tutorial07.txt b/docs/intro/tutorial07.txt
index a8d5e61b81..bf695d551c 100644
--- a/docs/intro/tutorial07.txt
+++ b/docs/intro/tutorial07.txt
@@ -422,7 +422,7 @@ The template to customize is ``admin/index.html``. (Do the same as with
 ``admin/base_site.html`` in the previous section -- copy it from the default
 directory to your custom template directory). Edit the file, and you'll see it
 uses a template variable called ``app_list``. That variable contains every
-installed Django app. Instead of using that, you can hard-code links to
+installed Django app. Instead of using that, you can hardcode links to
 object-specific admin pages in whatever way you think is best.
 
 When you're comfortable with the admin, read :doc:`part 8 of this