Skip to content
This repository
Browse code

Less annoying gender neutral forms

  • Loading branch information...
commit 22d468e190c4cdd3af8ea0546157f22b53197855 1 parent d3b0edb
Armin Ronacher authored
2  docs/api.rst
Source Rendered
@@ -156,7 +156,7 @@ If you have the :attr:`Flask.secret_key` set you can use sessions in Flask
156 156 applications. A session basically makes it possible to remember
157 157 information from one request to another. The way Flask does this is by
158 158 using a signed cookie. So the user can look at the session contents, but
159   -not modify it unless he or she knows the secret key, so make sure to set that
  159 +not modify it unless they know the secret key, so make sure to set that
160 160 to something complex and unguessable.
161 161
162 162 To access the current session you can use the :class:`session` object:
4 docs/patterns/errorpages.rst
Source Rendered
@@ -24,7 +24,7 @@ even if the application behaves correctly:
24 24 *403 Forbidden*
25 25 If you have some kind of access control on your website, you will have
26 26 to send a 403 code for disallowed resources. So make sure the user
27   - is not lost when he or she tries to access a forbidden resource.
  27 + is not lost when they try to access a forbidden resource.
28 28
29 29 *410 Gone*
30 30 Did you know that there the "404 Not Found" has a brother named "410
@@ -32,7 +32,7 @@ even if the application behaves correctly:
32 32 resources that previously existed and got deleted answer with 410
33 33 instead of 404. If you are not deleting documents permanently from
34 34 the database but just mark them as deleted, do the user a favour and
35   - use the 410 code instead and display a message that what he or she was
  35 + use the 410 code instead and display a message that what they were
36 36 looking for was deleted for all eternity.
37 37
38 38 *500 Internal Server Error*
2  docs/patterns/flashing.rst
Source Rendered
@@ -4,7 +4,7 @@ Message Flashing
4 4 ================
5 5
6 6 Good applications and user interfaces are all about feedback. If the user
7   -does not get enough feedback he or she will probably end up hating the
  7 +does not get enough feedback they will probably end up hating the
8 8 application. Flask provides a really simple way to give feedback to a
9 9 user with the flashing system. The flashing system basically makes it
10 10 possible to record a message at the end of a request and access it next
2  docs/patterns/viewdecorators.rst
Source Rendered
@@ -8,7 +8,7 @@ functionality to one or more functions. The :meth:`~flask.Flask.route`
8 8 decorator is the one you probably used already. But there are use cases
9 9 for implementing your own decorator. For instance, imagine you have a
10 10 view that should only be used by people that are logged in to. If a user
11   -goes to the site and is not logged in, he or she should be redirected to the
  11 +goes to the site and is not logged in, they should be redirected to the
12 12 login page. This is a good example of a use case where a decorator is an
13 13 excellent solution.
14 14
8 docs/quickstart.rst
Source Rendered
@@ -126,7 +126,7 @@ Modern web applications have beautiful URLs. This helps people remember
126 126 the URLs which is especially handy for applications that are used from
127 127 mobile devices with slower network connections. If the user can directly
128 128 go to the desired page without having to hit the index page it is more
129   -likely he or she will like the page and come back next time.
  129 +likely they will like the page and come back next time.
130 130
131 131 As you have seen above, the :meth:`~flask.Flask.route` decorator is used
132 132 to bind a function to a URL. Here are some basic examples::
@@ -614,7 +614,7 @@ code use the :func:`~flask.abort` function. Here an example how this works::
614 614 this_is_never_executed()
615 615
616 616 This is a rather pointless example because a user will be redirected from
617   -the index to a page he or she cannot access (401 means access denied) but it
  617 +the index to a page they cannot access (401 means access denied) but it
618 618 shows how that works.
619 619
620 620 By default a black and white error page is shown for each error code. If
@@ -641,7 +641,7 @@ Besides the request object there is also a second object called
641 641 user from one request to the next. This is implemented on top of cookies
642 642 for you and signs the cookies cryptographically. What this means is that
643 643 the user could look at the contents of your cookie but not modify it,
644   -unless he or she knows the secret key used for signing.
  644 +unless they know the secret key used for signing.
645 645
646 646 In order to use sessions you have to set a secret key. Here is how
647 647 sessions work::
@@ -697,7 +697,7 @@ Message Flashing
697 697 ----------------
698 698
699 699 Good applications and user interfaces are all about feedback. If the user
700   -does not get enough feedback he or she will probably end up hating the
  700 +does not get enough feedback they will probably end up hating the
701 701 application. Flask provides a really simple way to give feedback to a
702 702 user with the flashing system. The flashing system basically makes it
703 703 possible to record a message at the end of a request and access it next
2  docs/security.rst
Source Rendered
@@ -73,7 +73,7 @@ them knowing.
73 73 Say you have a specific URL that, when you sent `POST` requests to will
74 74 delete a user's profile (say `http://example.com/user/delete`). If an
75 75 attacker now creates a page that sends a post request to that page with
76   -some JavaScript he or she just has to trick some users to load that page and
  76 +some JavaScript they just has to trick some users to load that page and
77 77 their profiles will end up being deleted.
78 78
79 79 Imagine you were to run Facebook with millions of concurrent users and
2  docs/tutorial/introduction.rst
Source Rendered
@@ -8,7 +8,7 @@ less web-2.0-ish name ;) Basically we want it to do the following things:
8 8
9 9 1. let the user sign in and out with credentials specified in the
10 10 configuration. Only one user is supported.
11   -2. when the user is logged in he or she can add new entries to the page
  11 +2. when the user is logged in they can add new entries to the page
12 12 consisting of a text-only title and some HTML for the text. This HTML
13 13 is not sanitized because we trust the user here.
14 14 3. the page shows all entries so far in reverse order (newest on top) and
2  docs/tutorial/views.rst
Source Rendered
@@ -29,7 +29,7 @@ The view function will pass the entries as dicts to the
29 29 Add New Entry
30 30 -------------
31 31
32   -This view lets the user add new entries if he or she is logged in. This only
  32 +This view lets the user add new entries if they are logged in. This only
33 33 responds to `POST` requests, the actual form is shown on the
34 34 `show_entries` page. If everything worked out well we will
35 35 :func:`~flask.flash` an information message to the next request and

0 comments on commit 22d468e

Please sign in to comment.
Something went wrong with that request. Please try again.