letro/letro-android
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity

Grammar fixes for docs and comments (#5043)

Browse Source
This commit is contained in:
Andy Balaam
2025-07-17 19:32:37 +01:00
committed by GitHub
parent 8de5bd220e
commit 6752146061
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/notifications.md
View File

@@ -149,7 +149,7 @@ That is why clients are able to **process the push rules client side** to decide
As seen previously, App developers don't directly send a push to the end user's device, they use a Push Provider as intermediary. So technically this intermediary is able to read the content of what is sent.
App developers usually mitigate this by sending a `silent notification`, that is a notification with no identifiable data, or with an encrypted payload. When the push is received the app can then synchronise to it's server in order to generate a local notification.
App developers usually mitigate this by sending a `silent notification`, that is a notification with no identifiable data, or with an encrypted payload. When the push is received the app can then synchronise to its server in order to generate a local notification.
### Background processing limitations