From 20cb42616b46f5830c04be80e4ea2e71f9d0ec9d Mon Sep 17 00:00:00 2001
From: Game_Time <108236317+RayBytes@users.noreply.github.com>
Date: Sat, 16 Aug 2025 00:42:13 +0500
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 56cb7b1..d06d83f 100644
--- a/README.md
+++ b/README.md
@@ -81,13 +81,13 @@ curl http://127.0.0.1:8000/v1/chat/completions \
 
 ### Thinking effort
 
+- `--reasoning-effort` (choice of low,medium,high)
 GPT-5 has a configurable amount of "effort" it can put into thinking, which may cause it to take more time for a response to return, but may overall give a smarter answer. Applying this parameter after `serve` forces the server to use this reasoning effort by default, unless overrided by the API request with a different effort set. The default reasoning effort without setting this parameter is `medium`.
-`--reasoning-effort` (choice of low,medium,high)
 
 ### Thinking summaries
 
+- `--reasoning-summary` (choice of auto,concise,detailed,none)
 Models like GPT-5 do not return raw thinking content, but instead return thinking summaries. These can also be customised by you.
-`--reasoning-summary` (choice of auto,concise,detailed,none)
 
 ## Notes
 If you wish to have the fastest responses, I'd recommend setting `--reasoning-effort` to low, and `--reasoning-summary` to none.