docs: fix warnings in links (#4672)

docs/docs/cloud/how-tos/add-human-in-the-loop.md

@@ -8,7 +8,7 @@ Please see [the overview of LangGraph human-in-the-loop](../../concepts/human_in
 
 The [`interrupt` function][langgraph.types.interrupt] in LangGraph enables human-in-the-loop workflows by pausing the graph at a specific node, presenting information to a human, and resuming the graph with their input. It's useful for tasks like approvals, edits, or gathering additional context.
 
-The graph is resumed using a [`Command`](../reference/types.md#langgraph.types.Command) object that provides the human's response.
+The graph is resumed using a [`Command`][langgraph.types.Command] object that provides the human's response.
 
 **Graph node with `interrupt`:**
 

docs/docs/cloud/how-tos/clone_traces_studio.md

@@ -14,7 +14,7 @@ To support this, LangGraph Studio, in combination with LangSmith, allows you to
     - langgraph-api>=0.0.32
 
 - A thread traced in LangSmith.
-- A locally running agent. See [here](../../how-tos/local-studio.md) for setup instructions.
+- A locally running agent. See [here](../how-tos/studio/quick_start.md#local-development-server) for setup instructions.
   - Note that your local agent must be using the above specified `langgraph` and `langgraph-api` versions.
   - The nodes present in the remote trace must exist in at least one of the graphs in your local agent.
 

docs/docs/cloud/how-tos/studio/faqs.md

@@ -8,7 +8,7 @@ A project may fail to start if the configuration file is defined incorrectly, or
 
 When you select the `Interrupts` dropdown and select a node to interrupt the graph will pause execution before and after (unless the node goes straight to `END`) that node has run. This means that you will be able to both edit the state before the node is ran and the state after the node has ran. This is intended to allow developers more fine-grained control over the behavior of a node and make it easier to observe how the node is behaving. You will not be able to edit the state after the node has ran if the node is the final node in the graph.
 
-For more information on interrupts and human in the loop, see [here](./human_in_the_loop.md).
+For more information on interrupts and human in the loop, see [here](../../../concepts/human_in_the_loop.md).
 
 ## Why are extra edges showing up in my graph?
 

docs/docs/cloud/how-tos/use_stream_react.md

@@ -158,7 +158,7 @@ export default function HomePage() {
 }
 ```
 
-Under the hood, the `useStream()` hook will use the `streamMode: "messages-tuple"` to receive a stream of messages (i.e. individual LLM tokens) from any LangChain chat model invocations inside your graph nodes. Learn more about messages streaming in the [How to stream messages from your graph](./stream_messages.md) guide.
+Under the hood, the `useStream()` hook will use the `streamMode: "messages-tuple"` to receive a stream of messages (i.e. individual LLM tokens) from any LangChain chat model invocations inside your graph nodes. Learn more about messages streaming in the [streaming](../how-tos/streaming.md#messages) guide.
 
 ### Interrupts
 
@@ -476,7 +476,7 @@ The `useStream()` hook provides several callback options to help you respond to
 - `onError`: Called when an error occurs.
 - `onFinish`: Called when the stream is finished.
 - `onUpdateEvent`: Called when an update event is received.
-- `onCustomEvent`: Called when a custom event is received. See [Custom events](../../how-tos/streaming.ipynb#custom) to learn how to stream custom events.
+- `onCustomEvent`: Called when a custom event is received. See the [streaming](../../how-tos/streaming.md#stream-custom-data) guide to learn how to stream custom events.
 - `onMetadataEvent`: Called when a metadata event is received, which contains the Run ID and Thread ID.
 
 ## Learn More