From 1ea11365f61a78051e196e6123d5f987efa90df1 Mon Sep 17 00:00:00 2001 From: Cerebro Cerberus Date: Wed, 28 Jun 2023 05:08:51 +0000 Subject: [PATCH] [4.2.x] Fixed typo in docs/intro/tutorial08.txt. Backport of 6fbe5287ac46f38faa9634e02da7e7b01e37c34d from main --- docs/intro/tutorial08.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/intro/tutorial08.txt b/docs/intro/tutorial08.txt index e33a02ec2c..5a20e29b9d 100644 --- a/docs/intro/tutorial08.txt +++ b/docs/intro/tutorial08.txt @@ -83,7 +83,7 @@ depends on your needs and goals. Sometimes it's fine to use a package that's in its alpha state. Other times, you need to know it's production ready. `Adam Johnson has a blog post `_ that outlines -a set of characteristics a that qualifies a package as "well maintained". +a set of characteristics that qualifies a package as "well maintained". Django Packages shows data for some of these characteristics, such as when the package was last updated.