> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# Creating Pull Requests

> Submit a pull request to the Hedera docs: fork the repo, sign off your commits, follow the style guide, and pass the validation checks before requesting review.

If you'd like to propose changes directly to the documentation, you can submit a pull request. Here's how:

1. **Fork the Repository:** Navigate to the `hedera-docs` [repository](https://github.com/hashgraph/hedera-docs) and click the "Fork" button at the top right. This creates a copy of the repository in your GitHub account.
2. **Clone the Forked Repository:** Clone the forked repository to your local system and make changes. Be sure to follow the repository's coding and style guidelines.
3. **Commit Your Changes:** Once you've made your changes, commit them with a clear, detailed message describing the changes you've made.
   1. Use [sign-off](https://github.com/hashgraph/.github/blob/main/CONTRIBUTING.md#sign-off) when making each of your commits.
      1. Alternatively, you can use auto sign-off by installing `cp hooks-git/prepare-commit-msg .git/hooks && chmod +x .git/hooks/prepare-commit-msg`
   2. Use [this guide](https://pre-commit.com/#3-install-the-git-hook-scripts) to install the pre-commit hook scripts to check for files with names that would conflict on a case-insensitive filesystem like MacOS HFS+ or Windows FAT.
4. **Push Your Changes:** Push your committed changes to your forked repository on GitHub.
5. **Submit a Pull Request:** Back in the `hedera-docs` repository, click the "Pull Requests" tab and then the "New pull request" button. Select your forked repository and the branch containing your changes, then click "Create pull request".
6. **Describe Your Changes:** Give your pull request a title and describe the proposed changes. This description should make it clear why the changes should be incorporated.
7. **Submit the Pull Request:** Click the "Create pull request" button to submit it. We'll review your proposed changes and, if they're approved, merge them into the repository.

By logging issues and creating pull requests, you're helping us make the Hedera documentation better for everyone. We appreciate your contributions and look forward to collaborating with you!

<Info>
  **Note:** The Hedera team will review issues and pull requests.
</Info>

## Controlled vocabulary

Hedera documentation uses a controlled vocabulary for accounts, EVM addresses, and aliases (for example, **EVM Address from Public Key** and **EVM Address from Account ID**). A few legacy terms are retired and are blocked automatically: a pull request that introduces a retired term in docs will fails the **Terminology Check** workflow, which reads its word list from [`.github/terminology-banned.txt`](https://github.com/hashgraph/hedera-docs/blob/main/.github/terminology-banned.txt). If your PR fails that check, the annotation tells you which term to replace. See the [glossary](/support/glossary) for the canonical definitions.