diff options
| author | Sebastian Kriems <skriems> | 2016-01-15 08:50:40 +0000 |
|---|---|---|
| committer | Sebastian Kriems <skriems> | 2016-01-15 08:50:40 +0000 |
| commit | d2561fa2b9b71de3938ac778ee545e768df1703f (patch) | |
| tree | 29c7bdac7301fe24f7937b20c2665d8e05b059f4 | |
| parent | 68c71f8fc8a51a788f89c17c10ad6088162136db (diff) | |
| download | cherrypy-d2561fa2b9b71de3938ac778ee545e768df1703f.tar.gz | |
minor typos
| -rw-r--r-- | docs/tutorials.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/tutorials.rst b/docs/tutorials.rst index 9163d309..36994a32 100644 --- a/docs/tutorials.rst +++ b/docs/tutorials.rst @@ -738,7 +738,7 @@ this is not the right way of keeping your data on the long run. Sessions are there to identify your user and carry as little amount of data as necessary for the operation carried by the user. -To store, persist and query data your need a proper database server. +To store, persist and query data you need a proper database server. There exist many to choose from with various paradigm support: - relational: PostgreSQL, SQLite, MariaDB, Firebird @@ -1131,7 +1131,7 @@ In order to understand them, let's imagine you are at a superstore: to make sure sections are always in order (this is your backend) In spite of being really simplistic, this is not far from how your -application behaves. CherryPy helps your structure your application +application behaves. CherryPy helps you structure your application in a way that mirrors these high-level ideas. Dispatchers |