Fix apparent power typo #2452
Fix apparent power typo #2452
Conversation
📝 WalkthroughWalkthroughThe documentation for the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Documentation
User->>Documentation: Request information on number entity
Documentation-->>User: Provide updated documentation
User->>Documentation: Review constant names and properties
Documentation-->>User: Display corrected constant and refined descriptions
Warning Rate limit exceeded@mikey0000 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 23 minutes and 10 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
docs/core/entity/number.md (1)
34-34: Consider standardizing table formatting.For consistency in markdown formatting, consider removing the trailing pipe at the end of the table row. While this is a minor formatting issue, it helps maintain a consistent style throughout the documentation.
-| `NumberDeviceClass.APPARENT_POWER` | VA | Apparent power | +| `NumberDeviceClass.APPARENT_POWER` | VA | Apparent power🧰 Tools
🪛 Markdownlint
34-34: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style(MD055, table-pipe-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
docs/core/entity/number.md(1 hunks)
🧰 Additional context used
🪛 Markdownlint
docs/core/entity/number.md
34-34: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style
(MD055, table-pipe-style)
🔇 Additional comments (1)
docs/core/entity/number.md (1)
34-34: LGTM! Spelling correction is accurate.
The change from "APPARANT_POWER" to "APPARENT_POWER" correctly fixes the spelling while maintaining the accurate technical specification (VA unit for apparent power measurement).
🧰 Tools
🪛 Markdownlint
34-34: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style
(MD055, table-pipe-style)
mikey0000
changed the title
MartinHjelmare
changed the title
Proposed change
Typo
Type of change
Additional information
Summary by CodeRabbit
numberentity.