diff options
author | Cristián Arenas Ulloa <cristian.arenas@gmail.com> | 2017-05-18 02:47:25 +0200 |
---|---|---|
committer | Paul Beusterien <paulbeusterien@google.com> | 2017-05-17 17:47:25 -0700 |
commit | 9a710f297bc4d9a1131557c08eebcff6708345b4 (patch) | |
tree | 9b09924df4b16a6f81b80dc691f990f0dd1a3838 /Firebase/Auth/Docs | |
parent | ed4cec2ea9f56fcc26c8da467a70efea6e8a4472 (diff) |
Fix typos (#15)
Diffstat (limited to 'Firebase/Auth/Docs')
-rw-r--r-- | Firebase/Auth/Docs/threading.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Firebase/Auth/Docs/threading.md b/Firebase/Auth/Docs/threading.md index 2f5b782..9c48a74 100644 --- a/Firebase/Auth/Docs/threading.md +++ b/Firebase/Auth/Docs/threading.md @@ -2,7 +2,7 @@ This document describes how Firebase Auth maintains thread-safety. The Firebase Auth library (not including Firebase Auth UI and Auth Provider UIs for now) -must be thread-safe, meaning deveopers are free to call any method in any +must be thread-safe, meaning developers are free to call any method in any thread at any time. Thus, all code that may take part in race conditions must be protected in some way. @@ -111,7 +111,7 @@ methods: * The calling code should already be in the auth global work queue. * The callback, if any, is provided by our own code, so it expects to called in the auth global work queue as well. This is usually already the case, - unless the method pass the callback to some other asychronous methods + unless the method pass the callback to some other asynchronous methods outside our library, in which case we need to manually make the callback called in the auth global work queue. |