@@ -99,7 +99,7 @@ This rule is almost the same as the default one, the only difference is that it
99
99
100
100
## Private (User Specific)
101
101
102
- This is where Firebase auth and rules are best used; each user can save their own data that they can only read and write.
102
+ This is where Firebase auth and rules are best used; each user can have their own data that they can only read and write.
103
103
104
104
A common example is an app where users can manage a todo list.
105
105
@@ -117,7 +117,7 @@ A common example is an app where users can manage a todo list.
117
117
```
118
118
119
119
We have a main ` todos ` node. Inside that node each user will have their own sub node.
120
- Each sub node wil contain the todos from the specified user.
120
+ Each sub node will contain the todos from the specified user.
121
121
122
122
The ` auth.uid ` parameter means the following:
123
123
@@ -182,7 +182,7 @@ Very similar to the previous one, the only difference is the `auth` parameter in
182
182
183
183
## Realtime Database
184
184
185
- Changes in the database can be read at realtime. Instead of using an ` URLRequest ` you must use an ` URLStream ` with a special ` URLRequestHeader ` .
185
+ Changes in the database can be read at realtime. Instead of using an ` URLLoader ` you must use an ` URLStream ` with a special ` URLRequestHeader ` .
186
186
187
187
In this case we specify to read the contents of the ` breakingnews ` node.
188
188
@@ -214,7 +214,7 @@ Remember to remove the event listener once you have finished working with the re
214
214
215
215
Auth works exactly the same as with non-realtime data, you only need to provide the ` auth ` parameter with a valid ` authToken ` in the URL.
216
216
217
- ## Modyfing the Database
217
+ ## Modifying the Database
218
218
219
219
You can add ` (INSERT) ` , remove ` (DELETE) ` and modify ` (UPDATE) ` data from the database. You only need to send your data ` JSON ` encoded.
220
220
0 commit comments