Skip to content

Commit cab514e

Browse files
author
Daniel Neuhäuser
committed
Merge pull request pallets#886 from talam/patch-1
Updated some typos
2 parents 5d20501 + b7f2183 commit cab514e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/tutorial/dbcon.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Step 3: Database Connections
44
----------------------------
55

66
We have created a function for establishing a database connection with
7-
`create_db` but by itself that's not particularly useful. Creating and
7+
`connect_db` but by itself that's not particularly useful. Creating and
88
closing database connections all the time is very inefficient, so we want
99
to keep it around for longer. Because database connections encapsulate a
1010
transaction we also need to make sure that only one request at the time
@@ -22,7 +22,7 @@ variable associated with the current application context. We will go into
2222
the details of this a bit later.
2323

2424
For the time being all you have to know is that you can store information
25-
savely on the :data:`~flask.g` object.
25+
safely on the :data:`~flask.g` object.
2626

2727
So when do you put it on there? To do that you can make a helper
2828
function. The first time the function is called it will create a database
@@ -67,7 +67,7 @@ Continue to :ref:`tutorial-dbinit`.
6767
where to put the code from this step and the next. A logical place is to
6868
group these module-level functions together, and put your new
6969
``get_db`` and ``close_db`` functions below your existing
70-
``init_db`` function (following the tutorial line-by-line).
70+
``connect_db`` function (following the tutorial line-by-line).
7171

7272
If you need a moment to find your bearings, take a look at how the `example
7373
source`_ is organized. In Flask, you can put all of your application code

0 commit comments

Comments
 (0)