docs: Remove no longer valid warning in useLLM hook doc (#608)

## Description

Update warning in versioned doc and removes warning from the current
version about using multiple instances of model runner in `useLLM` hook.

### Introduces a breaking change?

- [ ] Yes
- [x] No

### Type of change

- [ ] Bug fix (change which fixes an issue)
- [ ] New feature (change which adds functionality)
- [x] Documentation update (improves or adds clarity to existing
documentation)
- [ ] Other (chores, tests, code style improvements etc.)

### Tested on

- [ ] iOS
- [ ] Android

### Testing instructions

Build documentation and check that information is correct

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

Closes #607 

### Checklist

- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->

Author: msluszniak

docs/docs/02-hooks/01-natural-language-processing/useLLM.md

@@ -30,10 +30,6 @@ React Native ExecuTorch supports a variety of LLMs (checkout our [HuggingFace re
 Lower-end devices might not be able to fit LLMs into memory. We recommend using quantized models to reduce the memory footprint.
 :::
 
-:::caution
-Given computational constraints, our architecture is designed to support only one instance of the model runner at the time. Consequently, this means you can have only one active component leveraging `useLLM` concurrently.
-:::
-
 ## Initializing
 
 In order to load a model into the app, you need to run the following code:

docs/versioned_docs/version-0.5.x/02-hooks/01-natural-language-processing/useLLM.md

@@ -31,7 +31,7 @@ Lower-end devices might not be able to fit LLMs into memory. We recommend using
 :::
 
 :::caution
-Given computational constraints, our architecture is designed to support only one instance of the model runner at the time. Consequently, this means you can have only one active component leveraging `useLLM` concurrently.
+Up to version 0.5.3, our architecture was designed to support only one instance of the model runner at a time. As a consequence, only one active component could leverage `useLLM` concurrently. Starting with version 0.5.3, this limitation has been removed
 :::
 
 ## Initializing