Skip to content

Conversation

@Ashlesha-MSFT
Copy link
Contributor

@Ashlesha-MSFT Ashlesha-MSFT commented Nov 11, 2025

Category

  • Content fix
  • New article
  • Example checked item (delete this line)

Related issues

What's in this Pull Request?

Fix typos in formatting-syntax-reference and form-customizer docs

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 1a12873:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/declarative-customization/formatting-syntax-reference.md ⚠️Warning View Details
docs/spfx/extensions/get-started/building-form-customizer.md ✅Succeeded View

docs/declarative-customization/formatting-syntax-reference.md

  • Line 384, Column 223: [Warning: disallowed-html-tag - See documentation] HTML tag 'ItemID' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 294ab4f:

✅ Validation status: passed

File Status Preview URL Details
docs/declarative-customization/formatting-syntax-reference.md ✅Succeeded View
docs/spfx/extensions/get-started/building-form-customizer.md ✅Succeeded View

For more details, please refer to the build report.

@Ashlesha-MSFT
Copy link
Contributor Author

@Ashlesha-MSFT please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

@andrewconnell andrewconnell added the pr:in-review Actively reviewing pull request label Nov 12, 2025
@andrewconnell andrewconnell self-assigned this Nov 12, 2025
@andrewconnell
Copy link
Collaborator

Can't review until CLA is completed. @Ashlesha-MSFT please review & complete these instructiosn: #10474 (comment)

This is required for all submissions in this repo.

@andrewconnell andrewconnell added pr:do-not-merge Pull request not ready to be merged Needs: Author complete CLA Author has not signed the CLA. Contributions cannot be accepted into the docs unless & until the aut and removed pr:in-review Actively reviewing pull request labels Nov 12, 2025
@Ashlesha-MSFT
Copy link
Contributor Author

@andrewconnell,
I’ve completed the CLA as requested, and I’ve confirmed that all the checks have passed successfully on the PR.

@andrewconnell andrewconnell self-requested a review November 14, 2025 10:46
@andrewconnell andrewconnell added pr:in-review Actively reviewing pull request and removed pr:do-not-merge Pull request not ready to be merged Needs: Author complete CLA Author has not signed the CLA. Contributions cannot be accepted into the docs unless & until the aut labels Nov 14, 2025
- `id` is a property, so it should be formatted as code
- fixed other grammatical issues throughout doc
- update timestamp
@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

Copy link
Collaborator

@andrewconnell andrewconnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future, please separate two very different changes in different PRs

@andrewconnell andrewconnell added pr:ready-to-merge Ready to merge PR and removed pr:in-review Actively reviewing pull request labels Nov 14, 2025
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 7d49a47:

✅ Validation status: passed

File Status Preview URL Details
docs/declarative-customization/formatting-syntax-reference.md ✅Succeeded View
docs/spfx/extensions/get-started/building-form-customizer.md ✅Succeeded View

For more details, please refer to the build report.

@andrewconnell andrewconnell merged commit 0697611 into SharePoint:main Nov 14, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr:ready-to-merge Ready to merge PR

Projects

None yet

2 participants