From 885cb0d39041e359a3ad00d4bdaac24cbcc843c9 Mon Sep 17 00:00:00 2001
From: David Beitey <david@davidjb.com>
Date: Mon, 14 Jan 2019 23:54:15 +0000
Subject: [PATCH] Fixed "lets" mistakes in docs.

---
 docs/intro/tutorial01.txt      | 4 ++--
 docs/topics/forms/formsets.txt | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index db3340e702..208a4f3a3b 100644
--- a/docs/intro/tutorial01.txt
+++ b/docs/intro/tutorial01.txt
@@ -313,8 +313,8 @@ app will still work.
     You should always use ``include()`` when you include other URL patterns.
     ``admin.site.urls`` is the only exception to this.
 
-You have now wired an ``index`` view into the URLconf. Lets verify it's
-working, run the following command:
+You have now wired an ``index`` view into the URLconf. Verify it's working with
+the following command:
 
 .. console::
 
diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt
index eb84da40eb..0c4c7f0bee 100644
--- a/docs/topics/forms/formsets.txt
+++ b/docs/topics/forms/formsets.txt
@@ -687,7 +687,7 @@ Using more than one formset in a view
 You are able to use more than one formset in a view if you like. Formsets
 borrow much of its behavior from forms. With that said you are able to use
 ``prefix`` to prefix formset form field names with a given value to allow
-more than one formset to be sent to a view without name clashing. Lets take
+more than one formset to be sent to a view without name clashing. Let's take
 a look at how this might be accomplished::
 
     from django.forms import formset_factory