From 9173d79cca84d3c56a5e2d42620c3d0f67f684bc Mon Sep 17 00:00:00 2001 From: Namanv0509 Date: Mon, 19 Oct 2026 14:43:25 +0530 Subject: [PATCH] docs: fix broken image path for K8s proxy branch workflow Signed-off-by: Namanv0509 --- .../quickstart/k8s-proxy-developer-workflow.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-4.0.0/quickstart/k8s-proxy-developer-workflow.md b/versioned_docs/version-4.0.0/quickstart/k8s-proxy-developer-workflow.md index a68dad05c..16532ab87 100644 --- a/versioned_docs/version-4.0.0/quickstart/k8s-proxy-developer-workflow.md +++ b/versioned_docs/version-4.0.0/quickstart/k8s-proxy-developer-workflow.md @@ -45,7 +45,7 @@ There are two ways to create one. **Option A—From the dashboard.** Open your app → **Branches** → **Create branch** and enter a name (use your git branch name). -Create a Keploy branch from the dashboard +Create a Keploy branch from the dashboard **Option B—From the MCP server / REST API.** When you're driving Keploy from an IDE agent (Claude Code, Cursor, Windsurf), the agent calls the `create_branch` MCP tool. The same operation is also exposed as a plain REST endpoint for scripts and other automation. @@ -79,7 +79,7 @@ There are three ways to add or edit test data on the branch. Pick whichever matc **From the dashboard UI:** open the **Recordings** page, switch to your branch in the branch selector, and use the **+** menu to add a mock or edit an existing test case inline. Edits flow through the same branch overlay. -Edit mocks and test cases from the dashboard +Edit mocks and test cases from the dashboard **From the CLI (for whole test sets):** if you just recorded a new flow with `keploy record` on your laptop, upload the resulting `keploy/test-set-N/` directory as a single bundle: @@ -165,7 +165,7 @@ A reviewer (typically the same person reviewing the code PR) opens the URL the C After confirming the changes look right, the reviewer clicks **Approve**. The branch's status flips to `approved`, the gate stops blocking, and the next CI run on that PR turns green without any other change. -Branch diff and approval flow in the dashboard +Branch diff and approval flow in the dashboard ### 3. Merge the branch on PR merge