> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/marketing-studio/approving-or-editing-your-articles.md).
# Approving or editing your Articles
Edit a blog draft directly by clicking its text, add a cover image, title, description, or focus keyword, then approve the post or reject it for more work.
Open a draft to make any direct edits—simply click on the text to adjust formatting, correct content, or add personal touches.
### **Adding a cover image:**
You can also customize each draft by adding a **cover image**, and updating the title, description, or focus keyword. These options help streamline the process and prepare the post for easy publishing.
### **Approving Blog Posts**
When you’re ready, you can approve the blog post for finalization or reject it for further refinement.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dapta.ai/marketing-studio/approving-or-editing-your-articles.md?ask=&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.
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.
