Skip to content

docs(dsc-3.0): fix singular parameter() -> parameters() throughout dataTypes.md#403

Merged
michaeltlombardi merged 1 commit into
MicrosoftDocs:mainfrom
MukundaKatta:codex/fix-parameter-singular-in-datatypes-md
Apr 20, 2026
Merged

docs(dsc-3.0): fix singular parameter() -> parameters() throughout dataTypes.md#403
michaeltlombardi merged 1 commit into
MicrosoftDocs:mainfrom
MukundaKatta:codex/fix-parameter-singular-in-datatypes-md

Conversation

@MukundaKatta

Copy link
Copy Markdown
Contributor

Closes #401. The DSC template function is called parameters() (matching the Azure ARM-template convention), but the Data types reference page at dsc/docs-conceptual/dsc-3.0/reference/schemas/definitions/parameters/dataTypes.md writes it as parameter() in nine places across five code blocks, including the very first syntax example.

The issue explicitly called out the first four code blocks; this PR fixes those plus two further singular occurrences later in the Objects example (properties: "[parameter('tstoy')]" / properties: "[parameter('registryKeys').productName]") so the whole page uses the correct spelling. sed -n '149p' / '182p' already used parameters(), so the mixed usage on the same page is the real smell — this normalises it.

No prose or example semantics changed beyond the typo.

…taTypes.md

The DSC template function is called 'parameters()' (matching the
Azure ARM-template convention), but the 'Data types' reference page
at docs-conceptual/dsc-3.0/reference/schemas/definitions/parameters/dataTypes.md
wrote it as 'parameter()' in nine places, including the very first
syntax example block the article introduces.

As noted in MicrosoftDocs#401, the first four code blocks were affected; while
here, also fix the singular calls further down in the Objects
example (lines 173 and 177) so the whole page uses the correct
spelling.

No prose or example semantics changed beyond the typo.

Closes MicrosoftDocs#401.
@learn-build-service-prod

Copy link
Copy Markdown
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
Copy Markdown
Contributor

Learn Build status updates of commit 93fec50:

✅ Validation status: passed

File Status Preview URL Details
dsc/docs-conceptual/dsc-3.0/reference/schemas/definitions/parameters/dataTypes.md ✅Succeeded View (dsc-3.0)

For more details, please refer to the build report.

@michaeltlombardi michaeltlombardi merged commit 6f05c04 into MicrosoftDocs:main Apr 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Typo in the first 4 codeblocks

2 participants