diff --git a/Makefile b/Makefile
index fb9fd4def..2db157409 100644
--- a/Makefile
+++ b/Makefile
@@ -66,7 +66,7 @@ docs_serve:     ## Build docs and start frontend server
 docs_watch:     ## Build docs and watch for changes
 	python scripts/docs.py build --source docs --destination ${FRONTEND_PATH}/content/docs --watch
 
-docs_publish:   ## Tag and push `docs-next` ref
+docs_publish:   ## Tag and push `docs` ref
 	git tag -d docs && git tag docs && git push --force origin docs
 
 docs_publish_dev:   ## Tag and push `docs-next` ref
diff --git a/docs/5.advanced/8.mcp.md b/docs/5.advanced/8.mcp.md
index ab43acc9b..98b7c34f4 100644
--- a/docs/5.advanced/8.mcp.md
+++ b/docs/5.advanced/8.mcp.md
@@ -37,7 +37,7 @@ With DipDup's MCP integration, you can:
 
 There are three types of MCP primitives (citing from the docs):
 
-- **Resources** are **application-controlled** and allow to expose data and content that can be read by clients and used as context for LLM interactions.
+- **Resources** are **application-controlled** and allow servers to expose data and content that can be read by clients and used as context for LLM interactions.
 - **Tools** are **model-controlled** and enable servers to expose executable functionality to clients, such as interacting with external systems, performing computations, and taking actions in the real world.
 - **Prompts** are **user-controlled** and enable servers to define reusable prompt templates and workflows that clients can easily surface to users and LLMs
 
@@ -183,11 +183,11 @@ async def tool():
     result = await mcp.call_tool('my_tool', {})
 ```
 
-For a low-level access you can use `dipdup.mcp.server` singleton to interact with the running server.
+For low-level access, you can use `dipdup.mcp.server` singleton to interact with the running server.
 
 ### Interacting with running indexer
 
-DipDup provides [management API](../7.references/4.api.md) to interact with the running indexer. For example you can use it to add indexes in runtime.
+DipDup provides [management API](../7.references/4.api.md) to interact with the running indexer. For example, you can use it to add indexes at runtime.
 
 You can use `ctx.call_api` to get nice plaintext output or `ctx.api` to access the datasource directly.