re-use -> reuse

Author: YuriiMotov

docs/tutorial/create-db-and-table.md

@@ -152,7 +152,7 @@ Creating the **engine** is very simple, just call `create_engine()` with a URL f
 
 {* ./docs_src/tutorial/create_db_and_table/tutorial001_py310.py ln[1:16] hl[1,14] *}
 
-You should normally have a single **engine** object for your whole application and re-use it everywhere.
+You should normally have a single **engine** object for your whole application and reuse it everywhere.
 
 /// tip
 

docs/tutorial/fastapi/tests.md

@@ -253,7 +253,7 @@ Check out the number bubbles to see what is done by each line of code.
 
 But apart from the way we declare them and how we tell the framework that we want to have them in the function, they **work in a very similar way**.
 
-Now we create lots of tests and re-use that same fixture in all of them, saving us that **boilerplate code**.
+Now we create lots of tests and reuse that same fixture in all of them, saving us that **boilerplate code**.
 
 **pytest** will make sure to run them right before (and finish them right after) each test function. So, each test function will actually have its own database, engine, and session.
 

docs/tutorial/insert.md

@@ -159,7 +159,7 @@ In fact, the **session** needs and uses an **engine**.
 
 For example, if we have a web application, we would normally have a single **session** per request.
 
-We would re-use the same **engine** in all the code, everywhere in the application (shared by all the requests). But for each request, we would create and use a new **session**. And once the request is done, we would close the session.
+We would reuse the same **engine** in all the code, everywhere in the application (shared by all the requests). But for each request, we would create and use a new **session**. And once the request is done, we would close the session.
 
 The first step is to import the `Session` class:
 

docs/tutorial/many-to-many/create-data.md

@@ -61,7 +61,7 @@ INFO Engine INSERT INTO team (name, headquarters) VALUES (?, ?)
 INFO Engine [generated in 0.00037s] ('Z-Force', 'Sister Margaret's Bar')
 INFO Engine INSERT INTO team (name, headquarters) VALUES (?, ?)
 INFO Engine [cached since 0.001239s ago] ('Preventers', 'Sharp Tower')
-// Insert the link data last, to be able to re-use the created IDs
+// Insert the link data last, to be able to reuse the created IDs
 INFO Engine INSERT INTO heroteamlink (team_id, hero_id) VALUES (?, ?)
 INFO Engine [generated in 0.00026s] ((2, 3), (1, 1), (2, 1), (2, 2))
 // Commit and save the data in the database

docs_src/tutorial/fastapi/app_testing/tutorial001_py310/annotations/en/test_main_005.md

@@ -38,4 +38,4 @@
 
 6. Now in the dependency override function, we just return the same `session` object that came from outside it.
 
-    The `session` object comes from the parameter passed to the test function, and we just re-use it and return it here in the dependency override.
+    The `session` object comes from the parameter passed to the test function, and we just reuse it and return it here in the dependency override.