diff options
| author | Cerebro Cerberus <sethamek@gmail.com> | 2023-06-28 05:08:51 +0000 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-06-28 07:10:04 +0200 |
| commit | 1ea11365f61a78051e196e6123d5f987efa90df1 (patch) | |
| tree | 0a6e79f7c527c6cd519953ed16c7329c81c836e7 | |
| parent | 7b45fe01abac68ba5c0162529eb6378eec405099 (diff) | |
[4.2.x] Fixed typo in docs/intro/tutorial08.txt.
Backport of 6fbe5287ac46f38faa9634e02da7e7b01e37c34d from main
| -rw-r--r-- | docs/intro/tutorial08.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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 <https://adamj.eu/tech/2021/11/04/the-well-maintained-test/>`_ 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. |