From bc4204c9d0f03e1a57fddbb3dc99a3e446b7c8c4 Mon Sep 17 00:00:00 2001
From: Kevin Woo <3469532+kevinawoo@users.noreply.github.com>
Date: Mon, 26 Jan 2026 11:56:28 -0800
Subject: [PATCH] Fix formatting of Nexus Operation example list

---
 docs/encyclopedia/nexus-operations.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/encyclopedia/nexus-operations.mdx b/docs/encyclopedia/nexus-operations.mdx
index db872a2f74..f0ec5f3d59 100644
--- a/docs/encyclopedia/nexus-operations.mdx
+++ b/docs/encyclopedia/nexus-operations.mdx
@@ -161,7 +161,7 @@ Nexus Machinery on both sides handles the cross-namepace communication.
 
 For example, when you execute a Nexus Operation in a caller Workflow the following Namespace gRPC calls are made:
 
-1. **RespondWorkflowTaskCompleted ([ScheduleNexusOperation command](/references/commands#schedulenexusoperation)) is used by the caller Worker to schedule a Nexus Operation, which atomically hands off execution to the caller's Nexus Machinery.
+1. **RespondWorkflowTaskCompleted** ([ScheduleNexusOperation command](/references/commands#schedulenexusoperation)) is used by the caller Worker to schedule a Nexus Operation, which atomically hands off execution to the caller's Nexus Machinery.
 1. **PollNexusTaskQueue** is used by the handler Worker to receive a [Nexus Task](/tasks#nexus-task) to process, for example to start a Nexus Operation.
 1. **RespondNexusTaskCompleted** or **RespondNexusTaskFailed** is used by the handler Worker to return the Nexus Task result.
    When asked to start a Nexus Operation, the Nexus handler decides if the Operation will be synchronous or asynchronous.