# Content

`Appearance` → `Customize`→ `Fonts Plugin` → `Advanced Settings` → `Content`

The **content** section consists of seven controls:

**Content Typography**

The following CSS selectors are targeted:

```
.entry-content, .post-content, .page-content, .post-excerpt, .entry-summary, .entry-excerpt
```

**Title and H1 Typography**

The following CSS selectors are targeted:

```
.entry-title, .entry-title a, .post-title, .post-title a, .page-title, .entry-content h1, #content h1
```

**H2 Typography**

The following CSS selectors are targeted:

```
.entry-content h2, .post-content h2, .page-content h2, #content h2
```

**H3 Typography**

The following CSS selectors are targeted:

```
.entry-content h3, .post-content h3, .page-content h3, #content h3
```

**H4 Typography**

The following CSS selectors are targeted:

```
.entry-content h4, .post-content h4, .page-content h4, #content h4
```

**H5 Typography**

The following CSS selectors are targeted:

```
.entry-content h5, .post-content h5, .page-content h5, #content h5
```

**H6 Typography**

The following CSS selectors are targeted:

```
.entry-content h6, .post-content h6, .page-content h6, #content h6
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fontsplugin.com/advanced-settings/content.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.