In `@content/components/sensor/pzemdc.md`:
- Line 173: The markdown line uses triple backticks around inline code; change
it to use single backticks so the action names render correctly: replace the
malformed text containing ```on_offline``` and ```on_online``` with `on_offline`
and `on_online` (update the line where the action names appear in
content/components/sensor/pzemdc.md, referencing the tokens on_offline and
on_online).
- Around line 82-83: Replace the bold text used for the section title with a
proper Markdown heading and add a blank line before the fenced code block:
change the "**Example Config**" line to a heading (e.g., "## Example Config")
and ensure there is an empty line between that heading and the triple-backtick
```yaml fence so the code block renders correctly.
- Line 199: In content/components/sensor/pzemdc.md there are multiple
consecutive blank lines; remove the extra blank line(s) so only a single blank
line remains between paragraphs/sections (collapse any run of blank lines to a
single newline) to satisfy the static analysis rule.
- Around line 202-206: Replace the legacy Hugo shortcodes in
content/components/sensor/pzemdc.md (the instances of {{< docref
"/components/uart" >}}, {{< docref "/components/modbus" >}}, {{< docref
"/components/modbus_controller" >}}, {{< docref
"/components/sensor/modbus_controller" >}}, and {{< docref
"/components/sensor/total_daily_energy" >}}) with standard Markdown links; for
each shortcode use [display text](path) — e.g. replace {{< docref
"/components/uart" >}} with [Components: UART](/components/uart) (or a concise
human-friendly label you prefer) and do the same for the other four shortcodes,
ensuring the link paths match the quoted paths and the display text is clear and
consistent.
- Line 91: Update the pzemdc.md documentation to clarify the differing UART
"stop_bits" values: add a short note next to the pzemdc component example (the
native pzemdc example using stop_bits: 2) and next to the Modbus alternative
example (the Modbus-over-UART example using stop_bits: 1) stating that both
settings are correct for their respective methods — the native pzemdc driver
expects 2 stop bits, while the Modbus-over-UART configuration typically uses 1
stop bit — and include a one-line rationale that the native driver and Modbus
protocol expect different UART framing so users should keep the stop_bits as
shown for each method.

In `@content/components/sensor/pzemdc.md`:
- Line 98: Update the YAML comment "#Lets intiate the Modbus Controller:" to
correct spelling and punctuation by changing it to "#Let's initiate the Modbus
Controller:" so the contraction and the verb are correct.
- Line 93: Update the YAML/Markdown comment string "#Lets define the modbus to
use:" to use the correct contraction with an apostrophe; change the text to
"#Let's define the modbus to use:" so the comment reads correctly. Reference the
existing comment line "#Lets define the modbus to use:" in
content/components/sensor/pzemdc.md to locate and update it.
- Line 188: Update the inline YAML comment that currently reads "//additionally
lets zero all sensors as the device is offline" to use the correct contraction
by replacing "lets" with "let's" (i.e., "//additionally let's zero all sensors
as the device is offline") so the comment is grammatically correct.
- Line 84: Update the YAML comment string "Where is the modbus hardware connect
to?" to the correct grammar "Where is the modbus hardware connected to?" in the
sensor/pzemdc.md content (locate the comment text itself to change).
- Line 173: Replace the hyphenated phrase "off- or online" with "offline or
online" in the Scenario sentence that references the binary sensor id
bs_pzem_online so it reads: "A binary sensor (id: bs_pzem_online) shall indicate
if the device is offline or online."
- Around line 80-81: Replace the unclear introductory sentence that starts
"While its own component is great working for a basic setup, you may want to
have more possibilities while using modbus controller." with a clearer phrasing;
update it to something like: "The native component works great for basic setups,
but you may want more flexibility when using the Modbus controller." Ensure
"Modbus" is capitalized and the sentence flow is corrected in the pzemdc.md
introductory paragraph.
- Line 181: Replace the grammatically incorrect YAML comment "Also possible
writing it in lambdas:" with a corrected phrasing such as "Also possible to
write it using lambdas:" (or "Also possible to write it with lambdas:") so the
comment is clear; locate the exact comment string "Also possible writing it in
lambdas:" in the sensor/pzemdc.md content and update it accordingly.
- Around line 172-174: Add blank lines before and after the heading
"`on_offline` and `on_online` Action" and also ensure there is a blank line
immediately before the fenced code block starting with "```yaml" and one after
the closing "```" so the heading and code block are separated from surrounding
text; edit the markdown around the heading and the fenced code block in
content/components/sensor/pzemdc.md to insert those blank lines.