# fix: update broken README links from docs/guides/ to docs/learn/guides/

Two README links pointing to ./docs/guides/ 404'd after the docs were reorganized under ./docs/learn/guides/.

| | |
| --- | --- |
| Status | COPILOT-WRITTEN · MERGED |
| Source | github:pmndrs/zustand#3542 |
| Original | https://github.com/pmndrs/zustand/pull/3542 |
| Workspace | Showcase |
| Tags | github, code, docs |

## What it does

**A single-file change to README.md, 4 lines.**

Copilot opened this, so there is no author to ask. 1 file changed across 1 area of pmndrs/zustand, 2 added and 2 removed.

Two README links pointing to ./docs/guides/ 404'd after the docs were reorganized under ./docs/learn/guides/.

**Diagram: Where the change landed. Node size is not to scale; the line counts are exact.**

- zustand (1 files, 4 lines) [accent]
- Docs (1 file, 4 lines) [neutral]
- README.md (+2 −2) [bad]
- zustand -> Docs
- Docs -> README.md : heaviest

- **Written by an agent.** Copilot authored this change. The usual review shortcut, asking the person who wrote it, is not available, so everything a reviewer needs has to come from the diff itself.
- **Heaviest file.** README.md, +2 −2, which is 100% of the change.
- **No test changed.** 0 source files changed with no accompanying test edit.
- **Spread.** 1 files, 4 changed lines in total.

## How it works

**The largest single edit is in README.md.**

Quoted verbatim from the diff. This is the biggest hunk by changed lines, which is where a reviewer's attention usually belongs first.

```markdown
@@ -28,7 +28,7 @@ npm install zustand
 
 ## First create a store
 
-Your store is a hook! You can put anything in it: primitives, objects, functions. State has to be updated immutably and the `set` function [merges state](./docs/guides/immutable-state-and-merging.md) to help it.
+Your store is a hook! You can put anything in it: primitives, objects, functions. State has to be updated immutably and the `set` function [merges state](./docs/learn/guides/immutable-state-and-merging.md) to help it.
 
 ```jsx
 import { create } from 'zustand'
```

_README.md, +2 −2. The largest hunk in the largest file._

## File map

**Every file this change touches, heaviest first.**

Role is inferred from the path and risk from the path and the line count. Neither was read from the code.

| File | Role | Change | Risk |
| --- | --- | --- | --- |
| `README.md` | documentation | modified, +2 −2 | none |

## Receipts

**Where each number above comes from.**

All of it is arithmetic over the file list and the check results, so it can be recomputed from the source.

- **Claim.** Copilot wrote this change.
  - Evidence: copilot-swe-agent
  - Where: commit 9764ece
- **Claim.** 1 files changed, +2 −2.
  - Evidence: README.md (+2 −2)
  - Where: https://github.com/pmndrs/zustand/pull/3542
- **Claim.** README.md carries 100% of the changed lines.
  - Evidence: 4 of 4 changed lines
  - Where: README.md
- **Claim.** It arrived as 1 commit.
  - Evidence: fix: update broken README links from docs/guides/ to docs/learn/guides/
  - Where: commit 9764ece
- **Claim.** CI reports 0 failing of 30.
  - Evidence: Continuous Releases
  - Where: CI check: Continuous Releases
- **Claim.** The change drew 3 comments.
  - Evidence: [vc]: #HkcZuBTDy/BAXCAxApwTTqjBGfFA6nb21kB2sz+zR24=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJ6dXN0YW5kLWRl…
  - Where: comment by vercel[bot]

## Merge order

**A reading order for the review, not a deployment plan.**

Ordered by how expensive each part is to get wrong, which is a structural property rather than an informed one.

1. **Then README.md.** The largest single file in the change, +2 −2.
2. **Decide whether a test is needed.** Nothing in this change adds or edits one.

## What this brief could not check

- No language model read this change. Every statement here is computed from file paths, line counts, and CI status, so it describes the shape of the diff and not what the diff means.