Update section titles and descriptions for clarity

[OldSurferDude]

Changed "Triggering" to "Controlling" where appropriate (caused confusion) Example did not work, missing line " data: " and properly indented the "group" line

Proposed change

The use of the word Triggering caused confusion
The example for [now called] controlling an Insteon scene did not work

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:
• 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.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	1fc27e1
🔍 Latest deploy log	https://app.netlify.com/projects/home-assistant-docs/deploys/69f436c1fc12e600084e0d95
😎 Deploy Preview	https://deploy-preview-45124--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[Copilot]

Pull request overview

This PR updates the Insteon integration documentation to reduce confusion by renaming the “Triggering Insteon scenes” section to “Controlling Insteon scenes” and adjusts the related text and YAML example to match current action-call formatting.

Changes:

• Renamed the “Triggering Insteon scenes” section to “Controlling Insteon scenes” and updated an internal link to match.
• Updated wording around scene usage to prefer “controlling” terminology.
• Fixed the YAML example by adding the missing data: block and indenting group correctly under it.

Comments suppressed due to low confidence (1)

source/_integrations/insteon.markdown:130

• The parameter descriptions still use "trigger" (and one is missing ending punctuation) even though this section has been renamed to "Controlling Insteon scenes". Please update the descriptions to consistently use "control" wording and add a period to the insteon.scene_off description.

- **insteon.scene_on**
  - **group**: (required) The Insteon scene number to trigger.
- **insteon.scene_off**
  - **group**: (required) The Insteon scene to turn off