> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/venn-diagram/format.md).
# Format
The Venn diagram provides various options for configuring the appearance of the visualization. All format options can be found in the format tab.
Venn Diagram configuration panel -> Format
**Circle opacity**: Adjusts the transparency of the circles in the Venn diagram, allowing you to layer information effectively.
**Text opacity**: Controls the transparency of the text within the Venn diagram, enhancing readability against different backgrounds.
**Border width**: Specifies the thickness of the borders around the circles, enabling clearer distinction between different sections of the Venn diagram.
**Border opacity**: Adjusts the transparency of the borders around the circles, improving the visual hierarchy and emphasis within the Venn diagram.
---
# 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.infotopics.com/showmemore/features/venn-diagram/format.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.
