docs: fix linting issues on versioned docs

docusaurus/docs/reactnative/basics/client.mdx

@@ -31,11 +31,11 @@ const client = StreamChat.getInstance('api_key');
 **Usage of `StreamChat.getInstance()` available since [email protected].**
 
 <br />
-This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and retrieve
-it wherever you need it on your app to perform API calls. After calling it once, any following <code>
+This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and
+retrieve it wherever you need it on your app to perform API calls. After calling it once, any following <code>
   getInstance
-</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple StreamChat
-instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
+</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple
+StreamChat instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
 <br />
 <br />
 

docusaurus/docs/reactnative/state-and-offline-support/state-overview.mdx

@@ -30,11 +30,11 @@ const client = StreamChat.getInstance('api_key');
 **Usage of `StreamChat.getInstance()` available since [email protected].**
 
 <br />
-This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and retrieve
-it wherever you need it on your app to perform API calls. After calling it once, any following <code>
+This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and
+retrieve it wherever you need it on your app to perform API calls. After calling it once, any following <code>
   getInstance
-</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple StreamChat
-instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
+</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple
+StreamChat instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
 <br />
 <br />
 

docusaurus/reactnative_versioned_docs/version-3.x.x/basics/client.mdx

@@ -31,11 +31,11 @@ const client = StreamChat.getInstance('api_key');
 **Usage of `StreamChat.getInstance()` available since [email protected].**
 
 <br />
-This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and retrieve
-it wherever you need it on your app to perform API calls. After calling it once, any following <code>
+This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and
+retrieve it wherever you need it on your app to perform API calls. After calling it once, any following <code>
   getInstance
-</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple StreamChat
-instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
+</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple
+StreamChat instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
 <br />
 <br />
 

docusaurus/reactnative_versioned_docs/version-3.x.x/basics/stream_chat_with_navigation.mdx

@@ -21,13 +21,12 @@ The guidance provided makes the assumption you are using [React Navigation](http
 
 <code>createNativeStackNavigator</code> uses the native APIs <code>UINavigationController</code> on iOS and <code>
   Fragment
-</code> on Android. The <code>OverlayProvider</code> needs to exist in a view that can render content in front of the chat
-screen. Therefore using a <code>fullScreenModal</code> with <code>createNativeStackNavigator</code>, which uses <code>
+</code> on Android. The <code>OverlayProvider</code> needs to exist in a view that can render content in front of the
+chat screen. Therefore using a <code>fullScreenModal</code> with <code>createNativeStackNavigator</code>, which uses <code>
   UIModalPresentationFullScreen
-</code> on iOS and <code>modal</code> on Android, to render your chat screen will leave the <code>
-  OverlayProvider
-</code> rendered behind the chat. If you are having issues we suggest you get in touch with support and we can find a
-solution to your specific navigation arrangement.
+</code> on iOS and <code>modal</code> on Android, to render your chat screen will leave the <code>OverlayProvider</code> rendered
+behind the chat. If you are having issues we suggest you get in touch with support and we can find a solution to your
+specific navigation arrangement.
 
 :::
 

docusaurus/reactnative_versioned_docs/version-4.x.x/basics/client.mdx

@@ -31,11 +31,11 @@ const client = StreamChat.getInstance('api_key');
 **Usage of `StreamChat.getInstance()` available since [email protected].**
 
 <br />
-This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and retrieve
-it wherever you need it on your app to perform API calls. After calling it once, any following <code>
+This new Singleton pattern allows you to instantiate a unique StreamChat client, i.e create a StreamChat instance and
+retrieve it wherever you need it on your app to perform API calls. After calling it once, any following <code>
   getInstance
-</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple StreamChat
-instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
+</code> call will return the initial StreamChat instance. This will prevent you from accidentally creating multiple
+StreamChat instances, opening multiple WebSockets, and driving up your concurrent connections unnecessarily.
 <br />
 <br />
 

docusaurus/reactnative_versioned_docs/version-4.x.x/basics/stream_chat_with_navigation.mdx

@@ -21,13 +21,12 @@ The guidance provided makes the assumption you are using [React Navigation](http
 
 <code>createNativeStackNavigator</code> uses the native APIs <code>UINavigationController</code> on iOS and <code>
   Fragment
-</code> on Android. The <code>OverlayProvider</code> needs to exist in a view that can render content in front of the chat
-screen. Therefore using a <code>fullScreenModal</code> with <code>createNativeStackNavigator</code>, which uses <code>
+</code> on Android. The <code>OverlayProvider</code> needs to exist in a view that can render content in front of the
+chat screen. Therefore using a <code>fullScreenModal</code> with <code>createNativeStackNavigator</code>, which uses <code>
   UIModalPresentationFullScreen
-</code> on iOS and <code>modal</code> on Android, to render your chat screen will leave the <code>
-  OverlayProvider
-</code> rendered behind the chat. If you are having issues we suggest you get in touch with support and we can find a
-solution to your specific navigation arrangement.
+</code> on iOS and <code>modal</code> on Android, to render your chat screen will leave the <code>OverlayProvider</code> rendered
+behind the chat. If you are having issues we suggest you get in touch with support and we can find a solution to your
+specific navigation arrangement.
 
 :::