Improve formatting and clarity in API documentation

[minvoker]

Changes include:

• Fix file tree formatting for improved readability
• Standardize JavaScript code formatting across examples
• Correct grammar and phrasing in multiple sections
• Improve clarity of configuration notes

[minvoker]

@microsoft-github-policy-service agree

[prmerger-automator]

@minvoker : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit a315a01:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/static-web-apps/add-api.md	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

@cjk7989

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Improves the readability and clarity of the Static Web Apps “add API” documentation by fixing formatting in the file tree example and tightening phrasing/grammar in several instructional notes.

Changes:

• Fixes file tree indentation/structure under the api folder example.
• Improves grammar and consistency (hyphenation, phrasing) in step instructions and notes.
• Clarifies the GitHub Actions configuration note about framework-dependent values.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[learn-build-service-prod]

Learn Build status updates of commit 4d3b7d4:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/static-web-apps/add-api.md	✅Succeeded

For more details, please refer to the build report.