CloseableUtil.closeQuietly(in);

        // Verify heading metadata
        final String[] headings = extractData.getValues("headings");
        assertNotNull(headings);
        assertTrue(headings.length > 0);

        boolean foundIntroduction = false;
        boolean foundFeatures = false;
        for (final String heading : headings) {
            if (heading.contains("Introduction")) {
                foundIntroduction = true;

                    headings.add(headingText.toString());
                }
                super.visit(heading);
            }
        });

        if (!headings.isEmpty()) {
            extractData.putValues("headings", headings.toArray(new String[0]));
        }
    }

    /**
     * Extracts link URLs from the document.
     *
     * @param document the parsed Markdown document

1) Use clear, concise technical Chinese consistent with existing docs.
2) Address the reader naturally (commonly using “你/你的”).

### Headings

1) Follow existing Simplified Chinese heading style (short and descriptive).
2) Do not add trailing punctuation to headings.
3) If a heading contains only the name of a FastAPI feature, do not translate it.

### Quotes and punctuation

### Grammar and tone

1) Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
2) Keep the tone concise and technical.

### Headings

1) Follow existing Ukrainian heading style; keep headings short and instructional.
2) Do not add trailing punctuation to headings.

### Quotes

1) Prefer Ukrainian guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.

1) Use clear, concise technical Traditional Chinese consistent with existing docs.
2) Address the reader naturally (commonly using “你/你的”).

### Headings

1) Follow existing Traditional Chinese heading style (short and descriptive).
2) Do not add trailing punctuation to headings.

### Quotes and punctuation

  - extractor
  - markdown
---

# Introduction

This is a sample Markdown document for testing the MarkdownExtractor.

## Features

The extractor should handle:

- YAML front matter extraction
- Heading structure
- **Bold text** and *italic text*
- Lists and other formatting

### Code Examples

Here is some inline `code` and a code block:

```java
public class Example {

### Grammar and tone

1) Use polite, instructional Korean (e.g. 합니다/하세요 style).
2) Keep the tone consistent with the existing Korean FastAPI docs.

### Headings

1) Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
2) Do not add trailing punctuation to headings.

### Quotes

1) Keep quote style consistent with the existing Korean docs.

    page = context.new_page()
    page.goto("http://localhost:8000/docs")
    page.get_by_role("button", name="GET /items/ Read Items").click()
    page.get_by_role("button", name="Try it out").click()
    page.get_by_role("heading", name="Servers").click()
    # Manually add the screenshot
    page.screenshot(path="docs/en/docs/img/tutorial/query-param-models/image01.png")

    # ---------------------
    context.close()
    browser.close()

### Headings

1) Prefer translating headings using the infinitive form (as is common in the existing French docs): «Créer…», «Utiliser…», «Ajouter…».

2) For headings that are instructions written in imperative in English (e.g. “Go check …”), keep them in imperative in French, using the formal grammar (e.g. «Allez voir …»).

import okhttp3.internal.http.promisesBody
import okio.BufferedSource
import okio.Source
import okio.buffer

/**
 * Transparent Compressed response support.
 *
 * The algorithm map will be turned into a heading such as "Accept-Encoding: br, gzip"
 *
 * If [algorithms] is empty this interceptor has no effect. To disable compression set
 * a specific "Accept-Encoding: identity" or similar.
 *