> For the complete documentation index, see [llms.txt](https://docs.agora.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agora.foundation/guidelines/content/what-to-avoid.md).

# What to Avoid

###  **Overly Complicated Language**

* Don't use jargon or technical terms when simple words will do.
* Example to Avoid: "Leverage Agora's multifaceted digital interface for enhanced communal interaction."

###  **Lengthy Explanations for Simple Actions**

* Don't drown users in details for straightforward tasks.
* Example to Avoid: "To initiate the process of setting up your Agora profile, begin by navigating to the top right corner..."

###  **Negative or Passive Tone**

* Don't frame messages in a way that sounds pessimistic or passive.
* Example to Avoid: "Unfortunately, you might not find this feature easy to use..."

###  **Over-Promising or Hyperbolic Claims**

* Don't create unrealistic expectations about Agora’s features.
* Example to Avoid: "Agora will revolutionize every aspect of your digital life."

###  **Gendered or Exclusive Language**

* Don't use language that could be perceived as excluding any group.
* Example to Avoid: "Every businessman will find Agora’s networking tools useful."

###  **Overuse of Technical Details**

* Don't overload users with technicalities unless necessary.
* Example to Avoid: "Agora’s algorithm uses advanced cryptographic protocols..."

###  **Unnecessary Formality**

* Don't be overly formal; keep the tone friendly and approachable.
* Example to Avoid: "We hereby invite you to peruse the myriad features offered by Agora."

###  **Insensitive or Culturally Ignorant Statements**

* Don't make statements that could be offensive or show cultural insensitivity.
* Example to Avoid: "Agora is the Swiss Army knife of social platforms, handy for every scenario."

###  **Ambiguity in Instructions**

* Don't leave users confused about what actions to take.
* Example to Avoid: "Just click around and you’ll eventually figure out how to use Agora."

###  **Generic and Impersonal Messaging**

* Don't use blanket statements that don’t address specific user needs.
* Example to Avoid: "All users will enjoy every feature we have."

### **Remember**:

Agora's content should always be clear, concise, inclusive, and reflective of our community values. Avoiding these pitfalls ensures a more engaging and positive experience for all users.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.agora.foundation/guidelines/content/what-to-avoid.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.