Small typos fixed

Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>

docs/notifications.md

@@ -12,7 +12,7 @@ Please make sure you're using the latest version available on the AppStore. Push
 
 If you're using Talk 12 on the server, please make sure you're running atleast version 12.2.1 (see [here for details](https://github.com/nextcloud/spreed/pull/6329)).
 
-Please note that under rare circumstances apple will stop sending notifications to your device. Those situations will normally resolve automatically after 24h. If your problem still occurs after checking all the hints below and checked again after 24h, create an issue at https://github.com/nextcloud/talk-ios/issues
+Please note that under rare circumstances apple will stop sending (call-)notifications to your device. Those situations will usually resolve automatically after 24h. If your problem still occurs after checking all the hints below and you checked again after 24h, create an issue at https://github.com/nextcloud/talk-ios/issues
 
 ## 🍎 Check iOS settings
 
@@ -27,10 +27,10 @@ Please note that under rare circumstances apple will stop sending notifications
 
 - In the conversation settings (tap the conversation name while in a conversation), check that notifications are set to 
   "Always notify" or "Notify when mentioned".
-	- Be aware that this is a per conversation setting. Set it for every conversation differently depending on your 
+	- This is a per conversation setting. Set it for every conversation differently depending on your 
       needs.
     - If you're using Talk 13 or later, please note that notifications for chat messages and calls can be enabled/disabled independently for each conversation.
-- Also be aware that notifications are not generated when you have an active session for a conversation! This also applies for tabs that are open in the background, etc. You might want to check if there's still a browser open somewhere preventing notifications to be send to the device.
+- Also be aware that notifications are not generated when you have an active session for a conversation! This also applies for tabs that are open in the background, etc. You might want to check if there's still a browser open somewhere preventing notifications to be send to your device(s).
 
 ## 🖥 Check server settings
 
@@ -55,9 +55,9 @@ Data to encrypt is: {"nid":525210,"app":"admin_notification_talk","subject":"Tes
 Signed encrypted push subject
 Push notification sent successfully
 ```
-This means the notifications are set up correctly on the server side and a test-notification is send to your device(s). Please not that depending on the app version two things can happen:
+This means the notifications are set up correctly on the server side and a test-notification is send to your device(s). Please note that depending on the app version two things can happen:
 
-1. After about 30s a notification with the following text will be displayed: `You recieved a new notification that couldn't be decrypted`. This is totally fine and indicates, that push-notifications are working correctly. The version you're using doesn't support test-notifications, which results in this timeout and message.
+1. After about 30s a notification with the following text will be displayed: `You recieved a new notification that couldn't be decrypted`. This is totally fine and indicates, that push-notifications are working correctly. The version you're using doesn't support test-notifications, which results in the aforementioned timeout and message.
 2. You'll receive a notification with "Testing push notifications" almost immediately.
 
 If it prints something like