> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/project-control-center/v1-prior-version/tools/security/manage-non-inclusive-naming.md).
# Manage Non Inclusive Naming
## Adding Non Inclusive Words
You can add the words which depict people unfairly in an insulting manner and exclude people based on their ethnicity, gender or color. LFX will scan for these non inclusive words in the code. You refer Non Inclusive Language section for more information.
To add non inclusive words, perform the following steps:
1.Login into [PCC](https://projectadmin.lfx.linuxfoundation.org).
2\. Search for the required project. The Project dashboard appears. Click **Security** from the **LFX Tools STATUS** tab.
{% hint style="info" %}
You can also navigate to Security from the Vertical Sidebar navigation menu. Click **LFX Tools** and then select **Security**.
{% endhint %}
Security
3.The Security page appears. From the **Manage Inclusive Naming** tab, click **Proceed**.
4.Enter the non inclusive word in the **Add word** box and click **+Add**. The added non inclusive words are listed under NON-INCLUSIVE LANGUAGE.
## Deleting Non Inclusive Words
To delete a non inclusive word, perform the following steps:
1.From the **Manage Inclusive Naming** tab, click  icon that you want to delete from the list.
.png?alt=media)
2\. The Delete Keyword dialog box appears. Click **Delete** to confirm the deletion of the word.
---
# 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.linuxfoundation.org/lfx/project-control-center/v1-prior-version/tools/security/manage-non-inclusive-naming.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.
