typo fix in get_adc_voltage : get_adc_volatge->get_adc_voltage (AEGHB-1105)

[haruny]

This typo was really bugging my OCD

get_adc_voltage was previously spelled as get_adc_volatge
commit fixes the typo.

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• [n/a] Documentation is updated as needed.
• [ x] Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "Merge pull request #2 from espressif/master": probably contains Jira ticket reference (2025-07). Please remove Jira tickets from commit messages. the commit message "typo fix in get_adc_voltage : get_adc_volatge->get_adc_voltage": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

👋 Hello haruny, we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 9343b39

[CLAassistant]

All committers have signed the CLA.

[leeebo]

sha=9343b393dcb947be4672ad44d46534d1ed6f0ecf

[haruny]

this looks still open... anything needed on my end?

[leeebo]

@haruny You don't need to do anything at the moment. The internal process requires merging, testing and synchronization. This process will take some time. Sometimes if there are issues with other functional tests, they need to be fixed, which will also affect the final synchronization. Therefore, the time is uncertain.