docs: Fix command for versioning documentation (#952)

## Description

<!-- Provide a concise and descriptive summary of the changes
implemented in this PR. -->

### 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

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

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

### Related issues

<!-- Link related issues here using #issue-number -->

### 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/README.md

@@ -83,7 +83,7 @@ We use Docusaurus versioning to "freeze" documentation for older releases.
 When you release a new npm version (e.g., `1.0.0`), you must snapshot the documentation. Run this command from the `docs/` folder:
 
 ```bash
-yarn docusaurus docs:version 1.0.0
+yarn docs:version 1.0.0
 ```
 ### Why is this important?
 
@@ -109,4 +109,4 @@ This deletes the `.docusaurus` cache and `build` folder.
 TypeDoc runs strictly at startup. If you modify comments in the TypeScript package:
 
 1. Stop the server.
-2. Run `yarn start` again to regenerate the Markdown files.
+2. Run `yarn start` again to regenerate the Markdown files.