> For the complete documentation index, see [llms.txt](https://help.cabi.org/cabi-digital-library-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cabi.org/cabi-digital-library-help/search/british-american-spellings.md).

# British / American Spellings

The CABI Digital Library search functionality automatically finds British/American spelling variants across all content fields and full text, with the exception of the Keyword/Index fields where it looks for precise matches of spelling.&#x20;

{% hint style="info" %}
To look up the precise word or spelling variant of CABI’s index terms please use the [CABI Thesaurus](https://www.cabi.org/cabithesaurus/).&#x20;
{% endhint %}

A dedicated English dictionary is used to tackle the variations on word spelling caused by differences found among English speaking countries, and by alternative spellings within the same country.\
The varcon (Variant Conversion Info) lexicon is used to enhance English handling and it includes spellings in American, British, Canadian, and Australian and also variant spellings within these languages. British – US synonyms cannot be deactivated with double quotes.

Example: if you search for&#x20;

> *aa:chile*&#x20;

(aa = author affiliation)

The results will also give items with 'chili' in the author affiliation field, because this is considered a synonym of 'chile'.&#x20;

For indexing terms, truncation may also be used when searching to ensure that spelling variants are retrieved.

For example search for&#x20;

> *colo?r*&#x20;

rather than&#x20;

> *color*&#x20;

to ensure retrieval of any records where the word ‘colour” occurs as part of the index terms, for instance *“colour patterns*” in the descriptor fiel&#x64;*.*


---

# 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.cabi.org/cabi-digital-library-help/search/british-american-spellings.md?ask=<question>&goal=<user_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.
