[#3079] Corrected the 'appying' spelling in the '.env' provision description.

[AlexSkrypnyk]

Closes #3079

Summary

The PROVISION section comment in .env misspells applying as appying. This corrects the spelling in the root .env file and regenerates the installer test baseline fixture that mirrors it, so both copies of the comment stay identical.

Changes

• Corrected appying to applying in the PROVISION section comment in .env
• Regenerated .vortex/installer/tests/Fixtures/handler_process/_baseline/.env to carry the same correction, via the installer snapshot tooling

Before / After

┌───────────────────────────────────────────────────────────────────────────┐
│ BEFORE                                                                    │
│ # or fresh install from profile), running updates, appying configuration  │
│                                                                           │
│ AFTER                                                                     │
│ # or fresh install from profile), running updates, applying configuration │
└───────────────────────────────────────────────────────────────────────────┘

Summary by CodeRabbit

• Documentation
  • Corrected a spelling error in the provisioning documentation comment.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Team

Run ID: d07db515-84c4-41b8-93d5-12daaa29fff5

📥 Commits

Reviewing files that changed from the base of the PR and between 07d8658 and ba72848.

⛔ Files ignored due to path filters (1)

• .vortex/installer/tests/Fixtures/handler_process/_baseline/.env is excluded by !.vortex/installer/tests/Fixtures/**

📒 Files selected for processing (1)

• .env

Included review availability: 5 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 8 reviews per hour.

---

Walkthrough

The provisioning documentation comment in .env corrects “appiyng” to “applying”.

Changes

Provisioning documentation

Layer / File(s)	Summary
Correct provisioning comment .env	The provisioning description now uses the correct spelling, “applying”.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to ba728

This corrects the provisioning comment spelling without changing runtime behavior or configuration semantics. No merge-readiness risk remains.

Poem

A rabbit checks the spelling line
“Applying” now looks fine
The provision notes are clear
No typo hops from year to year
One small fix, and all is bright

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the spelling correction in the .env provision description and matches the linked issue.
Linked Issues check	✅ Passed	The reviewable change corrects the provisioning documentation typo in the root .env file, which satisfies issue #3079. The mirrored fixture is excluded by the path filter, so that additional synchroni…
Out of Scope Changes check	✅ Passed	The reviewable change is limited to the requested provisioning-description typo correction. No unrelated changes are indicated.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…

Full details: Linked Issues check

Explanation

The reviewable change corrects the provisioning documentation typo in the root .env file, which satisfies issue #3079. The mirrored fixture is excluded by the path filter, so that additional synchronization cannot be verified, but it is not required by the linked issue.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/env-provision-typo

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.56% (206/209)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[AlexSkrypnyk]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.56% (206/209)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[AlexSkrypnyk]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.56% (206/209)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.00%. Comparing base (07d8658) to head (ba72848).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3085      +/-   ##
==========================================
- Coverage   87.36%   87.00%   -0.36%     
==========================================
  Files         107      100       -7     
  Lines        5088     4925     -163     
  Branches       49        3      -46     
==========================================
- Hits         4445     4285     -160     
+ Misses        643      640       -3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

📖 Documentation preview for this pull request has been deployed to Netlify:

https://6a9904a0ea14d954694cfc06--vortex-docs.netlify.app

This preview is rebuilt on every commit and is not the production documentation site.