> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/doc-plugins/plugin-glpi-network/renamestrings.md).
# Renamer
(formerly "Rename GLPI strings" or "Local Override")
## Requirements (self-hosted)
| GLPI Version | Minimum PHP | Recommended |
| ------------ | ----------- | ----------- |
| 11.0.x | 8.2 | 8.4 |
| 12.0.X | 8.3 | 8.5 |
{% hint style="info" %}
A [GLPI Network BASIC](https://services.glpi-network.com/#offers) subscription (or higher) is required. This plugin is also available for all GLPI Network [Cloud instances](https://glpi-network.cloud).
{% endhint %}
***
## Download the plugin
* Go to **Marketplace**. Download and install the plugin **Rename GLPI strings**
***
## Creating an override
* Go to **Setup > Rename GLPI strings**
* Click on **Add** and select the appropriate language.
* In the **Override** tab, click on **New override**.
* Select the value you wish to change from the drop-down list. You can search directly.
We are going to change the value **Computer** to **PC**
* Select computer and enter the singular and plural of the word to be changed in the corresponding fields.
* Click on **Save**
***
## Show the change
You may not see the change immediately. To make it appear, log out and then log back in.
Before :
After :
***
## FAQ
If you have any questions about using the plugin, please consult our FAQ
Go to FAQ
---
# 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://help.glpi-project.org/doc-plugins/plugin-glpi-network/renamestrings.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.
