From d1a525472dd34e3c88282b344cccca37997375ec Mon Sep 17 00:00:00 2001 From: svlandeg Date: Wed, 17 Sep 2025 10:56:28 +0200 Subject: [PATCH 1/5] fix typo --- docs/tutorial/create-db-and-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/create-db-and-table.md b/docs/tutorial/create-db-and-table.md index 2f2f34c828..49e2862982 100644 --- a/docs/tutorial/create-db-and-table.md +++ b/docs/tutorial/create-db-and-table.md @@ -321,7 +321,7 @@ But you will learn about migrations later in the Advanced User Guide. Let's run the program to see it all working. -Put the code it in a file `app.py` if you haven't already. +Put the code in a file `app.py` if you haven't already. {* ./docs_src/tutorial/create_db_and_table/tutorial001_py310.py *} From c15d931cc522293eda3e357a9cc8c7184f30eabb Mon Sep 17 00:00:00 2001 From: svlandeg Date: Wed, 17 Sep 2025 12:30:45 +0200 Subject: [PATCH 2/5] fix typo --- docs/tutorial/one.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/one.md b/docs/tutorial/one.md index 54cdbbea93..63e6a9e448 100644 --- a/docs/tutorial/one.md +++ b/docs/tutorial/one.md @@ -106,7 +106,7 @@ In that case, instead of `.first()` we can use `.one()`: Here we know that there's only one `"Deadpond"`, and there shouldn't be any more than one. -If we run it once will output: +If we run it once, it will output:
From 7f99e288b12a3c87a4e7c82b6e5a89150f51f564 Mon Sep 17 00:00:00 2001 From: svlandeg Date: Wed, 17 Sep 2025 14:14:47 +0200 Subject: [PATCH 3/5] add missing word --- docs/tutorial/limit-and-offset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/limit-and-offset.md b/docs/tutorial/limit-and-offset.md index 215f57d1cd..7d847c59a7 100644 --- a/docs/tutorial/limit-and-offset.md +++ b/docs/tutorial/limit-and-offset.md @@ -10,7 +10,7 @@ Now let's see how to get only a **range of results**. ## Create Data -We will continue with the same code as before, but we'll modify it a little the `select_heroes()` function to simplify the example and focus on what we want to achieve here. +We will continue with the same code as before, but we'll modify it a little in the `select_heroes()` function to simplify the example and focus on what we want to achieve here. Again, we will create several heroes to have some data to select from: From beeace2d6f326999a5e7f8c773283e31be718a52 Mon Sep 17 00:00:00 2001 From: svlandeg Date: Wed, 17 Sep 2025 14:35:28 +0200 Subject: [PATCH 4/5] remove duplication --- docs/tutorial/connect/read-connected-data.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/connect/read-connected-data.md b/docs/tutorial/connect/read-connected-data.md index 3fd4607c92..2868c69dd5 100644 --- a/docs/tutorial/connect/read-connected-data.md +++ b/docs/tutorial/connect/read-connected-data.md @@ -129,7 +129,7 @@ And as we used `select` with two models, we will receive tuples of instances of {* ./docs_src/tutorial/connect/select/tutorial001_py310.py ln[61:66] hl[65] *} -For each iteration in the `for` loop we get a a tuple with an instance of the class `Hero` and an instance of the class `Team`. +For each iteration in the `for` loop we get a tuple with an instance of the class `Hero` and an instance of the class `Team`. And in this `for` loop we assign them to the variable `hero` and the variable `team`. From 7340b3dd611f068b6d3d25468b79460f70d9685b Mon Sep 17 00:00:00 2001 From: svlandeg Date: Wed, 17 Sep 2025 14:47:36 +0200 Subject: [PATCH 5/5] add : --- docs/tutorial/code-structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/code-structure.md b/docs/tutorial/code-structure.md index 6e377b89e4..60a4c432bf 100644 --- a/docs/tutorial/code-structure.md +++ b/docs/tutorial/code-structure.md @@ -145,7 +145,7 @@ Hero's team: name='Z-Force' headquarters='Sister Margaret's Bar' id=1 ## Make Circular Imports Work -Let's say that for some reason you hate the idea of having all the database models together in a single file, and you really want to have **separate files** a `hero_model.py` file and a `team_model.py` file. +Let's say that for some reason you hate the idea of having all the database models together in a single file, and you really want to have **separate files**: a `hero_model.py` file and a `team_model.py` file. You can also do it. 😎 There's a couple of things to keep in mind. 🤓