From 0e3394b75da37598485cc45b57e427402ad6ee21 Mon Sep 17 00:00:00 2001
From: tactino <18781106300@163.com>
Date: Fri, 18 Sep 2026 16:56:24 -0400
Subject: [PATCH 1/2] fix: the caption counted episodes the clip no longer
 shows

The gif was recut to one complete episode after the old one turned out to stop before the grasp finished, which left the caption claiming three.
---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index e0636bb..7a4fd56 100644
--- a/README.md
+++ b/README.md
@@ -11,9 +11,10 @@ from the feedback those clients send back.
      alt="A Franka arm in LIBERO reaching for and picking up an object, seen from the policy's own camera">
 
 *The **unmodified** pi0.5, driven through this server on `libero_spatial` task
-0 - three episodes, all three successful. These are the frames the env client
-sends as observations, at the policy's native 224x224, not an outside camera.
-The fine-tuned policy is the one that scores zero, below.*
+0 - one episode of the three that ran, all three successful. These are the
+frames the env client sends as observations, at the policy's native 224x224,
+not an outside camera. The fine-tuned policy is the one that scores zero,
+below.*
 
 **A full-size pi0.5 has run end to end through it on LIBERO** - inference,
 feedback and FPO training - with the server's record of episodes and steps

From df6e82769d9d5642348c376dd17a1dcb74807dce Mon Sep 17 00:00:00 2001
From: tactino <18781106300@163.com>
Date: Fri, 18 Sep 2026 17:01:31 -0400
Subject: [PATCH 2/2] fix: three install commands were rendering outside their
 code blocks

In the developer list the opening fence sat at four spaces while the command under it sat at two. Less indentation than the list item's content ends the item, so GitHub closed the list, rendered the command as a paragraph and printed the closing fence as literal text. The same two-space indent pulled the explanatory lines out of their items too.

Everything belonging to a list item is now at four spaces. Verified against the rendered HTML: the API returned exactly three stray fences, one per broken block.
---
 README.md | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 7a4fd56..b4f4f64 100644
--- a/README.md
+++ b/README.md
@@ -59,10 +59,10 @@ We use `uv` to manage dependencies and development environments.
 1. **Install uv** (if not already installed):
 
     ```bash
-  curl -LsSf https://astral.sh/uv/install.sh | sh
+    curl -LsSf https://astral.sh/uv/install.sh | sh
     ```
 
-  Or use your package manager (e.g., `brew install uv` on macOS).
+    Or use your package manager (e.g., `brew install uv` on macOS).
 
 2. **Clone the repository:**
 
@@ -71,22 +71,23 @@ We use `uv` to manage dependencies and development environments.
     cd plugrl-server
     ```
 
-  Nothing in the default install needs a git submodule. `pi0-policy` does -
-  see [Training PI0 (OpenPI) with FPO](#training-pi0-openpi-with-fpo)
-  for the extra steps a plain clone does not give you.
+    Nothing in the default install needs a git submodule. `pi0-policy` does -
+    see [Training PI0 (OpenPI) with FPO](#training-pi0-openpi-with-fpo)
+    for the extra steps a plain clone does not give you.
 
 3. **Install dependencies with uv:**
 
     ```bash
-  uv sync
+    uv sync
     ```
 
-  This will create a virtual environment at `.venv/` and install all dependencies specified in `pyproject.toml`.
+    This creates a virtual environment at `.venv/` and installs everything
+    `pyproject.toml` asks for.
 
 4. **Run commands via uv:**
 
     ```bash
-  uv run python -m plugrl_server.cli --help
+    uv run python -m plugrl_server.cli --help
     ```
 
 ### 🚀 Usage