Fix AirGradient name

[joostlek]

Proposed change

Fix AirGradient name

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase: Fix AirGradient name core#119046
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue: fixes #

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

• Documentation
  • Corrected capitalization of "AirGradient" in titles and descriptions.
  • Fixed sensor name from "PM0.03 count" to "PM0.3 count" in the AirGradient integration instructions for Home Assistant.

[home-assistant]

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

[coderabbitai]

Walkthrough

Walkthrough

The recent update focuses on correcting the capitalization of "AirGradient" and fixing a sensor name error in the AirGradient integration instructions for Home Assistant. Specifically, the title and description were updated to reflect the correct capitalization, and the sensor name was corrected from "PM0.03 count" to "PM0.3 count". These changes ensure accuracy and clarity in the documentation.

Changes

File Path	Change Summary
source/_integrations/airgradient.markdown	Updated title to "AirGradient", corrected description capitalization, and fixed sensor name from "PM0.03 count" to "PM0.3 count".

Sequence Diagram(s) (Beta)

The changes are purely textual and do not involve any new features or modifications to the control flow. Therefore, no sequence diagrams are necessary.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 73b3ed7 and de078d2.

Files selected for processing (1)

• source/_integrations/airgradient.markdown (3 hunks)

Additional context used

LanguageTool

source/_integrations/airgradient.markdown

[misspelling] ~20-~20: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...type: device ha_zeroconf: true --- The AirGradient integration will fetch data from your [...

---

[misspelling] ~20-~20: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ... integration will fetch data from your AirGradient devices....

Additional comments not posted (3)

source/_integrations/airgradient.markdown (3)

2-2: Corrected capitalization of "AirGradient" in the title.

---

3-3: Updated the description to reflect the correct capitalization of "AirGradient."

---

37-37: Corrected sensor name from "PM0.03 count" to "PM0.3 count" to match the standard notation for particulate matter.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	de078d2
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/6662b315cd9e050008f0d694
😎 Deploy Preview	https://deploy-preview-33126--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[frenck]

Thanks, @joostlek 👍

../Frenck