# Page Not Found

The URL `docs/go/go-in-action/9c7a5-d14c-c2a4-d2b8-c640-bca4-ce58-b9c8-d0b9` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [9장 테스트와 벤치마킹](https://docs.ocha.ng/go/go-in-action/9c7a5-d14c-c2a4-d2b8-c640-bca4-ce58-b9c8-d0b9.md)
- [8장 표준 라이브러리](https://docs.ocha.ng/go/go-in-action/8c7a5-d45c-c900-b77c-c774-be0c-b7ec-b9ac.md)
- [5장 GO의 타입 시스템](https://docs.ocha.ng/go/go-in-action/5c7a5-go-c758-d0c0-c785-c2dc-c2a4-d15c.md)
- [3장 패키지](https://docs.ocha.ng/go/go-in-action/3c7a5-d328-d0a4-c9c0.md)
- [7장 동시성 패턴](https://docs.ocha.ng/go/go-in-action/7c7a5-b3d9-c2dc-c131-d328-d134.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ocha.ng/go/go-in-action/9c7a5-d14c-c2a4-d2b8-c640-bca4-ce58-b9c8-d0b9.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.ocha.ng/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.ocha.ng/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/go/go-in-action/9c7a5-d14c-c2a4-d2b8-c640-bca4-ce58-b9c8-d0b9.md`).

You may also use `Accept: text/markdown` header for content negotiation.