[Doc][v0.18.0]Fix minimax2.5 readme (#8638)

<!--  Thanks for sending a pull request!

BEFORE SUBMITTING, PLEASE READ
https://docs.vllm.ai/en/latest/contributing/overview.html

-->
### What this PR does / why we need it?
<!--
- Please clarify what changes you are proposing. The purpose of this
section is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR.

- Please clarify why the changes are needed. For instance, the use case
and bug description.

- Fixes #
-->
Correct the descriptive errors in the document.

### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such
as API, interface or other behavior changes.
Documentation-only updates are not considered user-facing changes.
-->
no
### How was this patch tested?
<!--
CI passed with new added/existing test.
If it was tested in a way different from regular unit tests, please
clarify how you tested step by step, ideally copy and paste-able, so
that other reviewers can test and check, and descendants can verify in
the future.
If tests were not added, please describe why they were not added and/or
why it was difficult to add.
-->
doc test

---------

Signed-off-by: zjks98 <zhangjiakang4@huawei.com>
Co-authored-by: zjks98 <zhangjiakang4@huawei.com>

docs/source/tutorials/models/MiniMax-M2.md

@@ -104,7 +104,7 @@ docker run -itd -u 0 --ipc=host --privileged \
   --device /dev/davinci_manager \
   --device /dev/devmm_svm \
   --device /dev/hisi_hdc \
-  --shm-size=1200g \
+  --shm-size=1g \
   -v /usr/local/dcmi:/usr/local/dcmi \
   -v /usr/local/Ascend/driver/tools/hccn_tool:/usr/local/Ascend/driver/tools/hccn_tool \
   -v /usr/local/bin/npu-smi:/usr/local/bin/npu-smi \
@@ -112,7 +112,7 @@ docker run -itd -u 0 --ipc=host --privileged \
   -v /usr/local/Ascend/driver/version.info:/usr/local/Ascend/driver/version.info \
   -v /etc/ascend_install.info:/etc/ascend_install.info \
   -v /home/:/home/ \
-  -v /opt/data/verification/:/opt/data/verification/ \   # Map the model weights here
+  -v /opt/data/verification/:/opt/data/verification/ \
   -v /root/.cache:/root/.cache \
   -v /mnt/performance/:/mnt/performance/ \
   -it $IMAGE bash
@@ -426,9 +426,9 @@ Use vLLM bench for the **190k/1k, concurrency=4, 16 prompts** scenario:
 ```{code-block} bash
 vllm bench serve --backend vllm \
   --dataset-name prefix_repetition \
-  --prefix-repetition-prefix-len 175104 \   # Input: 190×1024 tokens with 90% prefix repetition
-  --prefix-repetition-suffix-len 19440 \    # Input: 190×1024 tokens minus the prefix length above
-  --prefix-repetition-output-len 1024 \     # Output: 1024 tokens
+  --prefix-repetition-prefix-len 175104 \
+  --prefix-repetition-suffix-len 19440 \
+  --prefix-repetition-output-len 1024 \
   --prefix-repetition-num-prefixes 1 \
   --num-prompts 16 \
   --max-concurrency 4 \