summaryrefslogtreecommitdiff
path: root/doc/reference/async.rst
diff options
context:
space:
mode:
authorJ Bradshaw <jbradsha@users.noreply.github.com>2015-05-23 20:28:22 +0100
committerXavier Morel <xmo@odoo.com>2015-07-07 12:09:21 +0200
commit2f7ab001e209fa54260bbc1dd008b9fa0e17baad (patch)
treed8ab5ffe63478450fdd9ee3af97ea4cc3b40b522 /doc/reference/async.rst
parent95e56a109d5abc97ab7db1ee1c9b9efb66a7e362 (diff)
[IMP] doc: grammar and readability
Backport of most of #6827 by J Bradshaw with additional modifications (and some reverts) during review. closes #6827
Diffstat (limited to 'doc/reference/async.rst')
-rw-r--r--doc/reference/async.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/reference/async.rst b/doc/reference/async.rst
index c2aded839aa..d8d9c7db90f 100644
--- a/doc/reference/async.rst
+++ b/doc/reference/async.rst
@@ -7,8 +7,8 @@ Asynchronous Operations
As a language (and runtime), javascript is fundamentally
single-threaded. This means any blocking request or computation will
-blocks the whole page (and, in older browsers, the software itself
-even preventing users from switching to an other tab): a javascript
+block the whole page (and, in older browsers, the software itself
+even preventing users from switching to another tab): a javascript
environment can be seen as an event-based runloop where application
developers have no control over the runloop itself.