docs: fix grammar and formatting

Author: HayesGordon

docusaurus/docs/reactnative/basics/upgrade_helper.mdx

@@ -6,9 +6,11 @@ title: Upgrading from V4
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
+This guide highlights the changes introduced from v4 to v5.
+
 ## Prop or Context Changes
 
-Following values in [`ImageGalleryContext`](https://getstream.io/chat/docs/sdk/reactnative/v5/contexts/image-gallery-context/#value) have been renamed
+The following values in [`ImageGalleryContext`](https://getstream.io/chat/docs/sdk/reactnative/v5/contexts/image-gallery-context/#value) have been renamed:
 
 - `image` -> `selectedMessage`
 - `setImage` -> `setSelectedMessage`
@@ -17,13 +19,13 @@ Following values in [`ImageGalleryContext`](https://getstream.io/chat/docs/sdk/r
 
 ## Dependency Changes
 
-- If you have installed `stream-chat` dependency explicitly on your application, then upgrade it to v7
+- If you have installed `stream-chat` dependency explicitly in your application, then upgrade it to v7:
 
   ```bash
   yarn add [email protected]
   ```
 
-- Replace [`@react-native-community/cameraroll`](https://github.com/react-native-cameraroll/react-native-cameraroll) dependency with [`@react-native-camera-roll/camera-roll`](https://www.npmjs.com/package/@react-native-camera-roll/camera-roll)
+- Replace [`@react-native-community/cameraroll`](https://github.com/react-native-cameraroll/react-native-cameraroll) dependency with [`@react-native-camera-roll/camera-roll`](https://www.npmjs.com/package/@react-native-camera-roll/camera-roll):
 
   ```bash
   yarn remove @react-native-community/cameraroll
@@ -32,52 +34,52 @@ Following values in [`ImageGalleryContext`](https://getstream.io/chat/docs/sdk/r
 
 ## Enable Offline Support
 
-Offline Support is a major opt-in feature introduced in v5 of SDK.
+Offline support is a major opt-in feature introduced in v5 of the Stream Chat React Native SDK.
 
 > Offline support is currently not implemented for Expo package (stream-chat-expo).
 
-Offline storage implementation currently offers following features:
+The offline storage implementation currently offers the following features:
 
-- access to chat when internet is disabled
-- faster loading of chat since chat gets loaded from offline storage first before loading data from network
-- syncing of database using websocket events and sync api.
+- Access to chat when Internet connection is disabled or low.
+- Faster startup times and loading, since initial data is loaded from offline storage before performing any network requests.
+- Syncing of the offline database using WebSocket events and Sync API.
 
-Following features are currently **NOT** implemented. They will be implemented gradually as part of minor releases in v5.
+The following features are currently **NOT** implemented. They will be implemented gradually as part of minor releases in v5.
 
-- optimistically update offline database during chat interactions such as send message, add reactions etc.
-- access to threads in offline mode
-- offline caching of attachment images and user images
+- Optimistically update offline database during chat interactions, such as send message, add reaction, etc.
+- Access to threads in offline mode.
+- Offline caching of attachment images and profile images.
 
-To enable offline support please follow the given steps:
+To enable offline support, please follow the given steps:
 
-- **Upgrade stream-chat dependency (optional)**
+1. **Upgrade stream-chat dependency (optional)**
 
-  If you have installed `stream-chat` dependency explicitly on your application, then upgrade it to v7
+  If you have installed `stream-chat` dependency explicitly on your application, then upgrade it to v7:
 
   ```bash
   yarn add [email protected]
   ```
 
-- **Add `react-native-quick-sqlite` dependency**
+2. **Add `react-native-quick-sqlite` dependency**
 
   ```bash
   yarn add react-native-quick-sqlite
   npx pod-install
   ```
 
-- **Ensure unique instance of Chat component**
+3. **Ensure a unique instance of Chat component**
 
-  Until v4, you could provide separate `Chat` component for each usage of `Channel` component or `ChannelList` component.
-  But from v5, it is necessary that you provide only one instance of `Chat` component within your application.
-  This component needs to be a parent for all the chat related components such as `ChannelList`, `Channel` or `Thread`.
+  Until v4, you could provide a separate `Chat` component for each usage of `Channel` component or `ChannelList` component.
+  But from v5, you must provide only one instance of the `Chat` component within your application.
+  This component needs to be a parent for all the chat-related components such as `ChannelList`, `Channel` or `Thread`.
 
-- **Do not wait for `connectUser` call to succeed**
+4. **Do not wait for `connectUser` call to succeed**
 
-  It is important that you call `connectUser` method on chat client, before you render Chat components.
+  It is important that you call the `connectUser` method on the chat client, before you render Chat components.
   But you don't need to wait for `connectUser` to succeed before rendering Chat components. This is to ensure:
 
   - Chat components have access to current user information, which is important to store/access offline data.
-  - In case of slow or no network, Chat components will still load the chat data without waiting for connectUser to succeed.
+  - In case of slow or no network access, Chat components will still load the chat data without waiting for `connectUser` to succeed.
 
   ```tsx {7,8,16}
   const chatClient = StreamChat.getInstance('API_KEY');
@@ -105,7 +107,7 @@ To enable offline support please follow the given steps:
   };
   ```
 
-- **Add `enableOfflineSupport` prop on Chat component**
+5. **Add `enableOfflineSupport` prop on Chat component**
 
   ```tsx
   import { Chat } from 'stream-chat-react-native';
@@ -115,11 +117,11 @@ To enable offline support please follow the given steps:
   </Chat>;
   ```
 
-- **Reset the database when signing out the user**
+6. **Reset the database when signing out the user**
 
-  Since SDK doesn't handle the app level authentication logic, its application's responsibility
-  to ensure resetting database when user gets logged out. This should be generally done before you
-  call `client.disconnectUser()`
+  Since the SDK doesn't handle app-level authentication logic, it's the application's responsibility
+  to ensure the database is reset when a user gets logged out. This should generally be done before you
+  call `client.disconnectUser()`.
 
   ```jsx
   import { QuickSqliteClient } from 'stream-chat-react-native';