Clarify Machine Configuration uses PSDSC

[Gijsreyn]

This PR clarifies that the current implementation of Machine Configuration uses PowerShell DSC, instead of Microsoft DSC.

[prmerger-automator]

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

[Gijsreyn]

@MutemwaRMasheke There was a discussion started on the DSC project. This led me to the following articles pointing towards Microsoft DSC, but Machine Configuration hasn't implemented the v3 engine yet. Can you perhaps take a look at this small PR for clarification?

[learn-build-service-prod]

Learn Build status updates of commit aaebce9:

💡 Validation status: suggestions

File	Status	Preview URL	Details
articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md	💡Suggestion		Details
articles/governance/machine-configuration/how-to/develop-custom-package/overview.md	💡Suggestion		Details

articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md

• Line 11, Column 28: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /powershell/dsc/overview?view=dsc-2.0

articles/governance/machine-configuration/how-to/develop-custom-package/overview.md

• Line 11, Column 28: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /powershell/dsc/overview?view=dsc-2.0

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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 5a046ea:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md	✅Succeeded
articles/governance/machine-configuration/how-to/develop-custom-package/overview.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 48a6619:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md	✅Succeeded
articles/governance/machine-configuration/how-to/develop-custom-package/overview.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[v-dirichards]

@michaeltlombardi

Can you review the proposed changes?

Due to the upcoming BUILD conference, all merging and publishing is on hold until the morning of May 19th.

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

[michaeltlombardi]

#sign-off

[v-dirichards]

@Gijsreyn @michaeltlombardi

Due to the upcoming BUILD conference, all merging and publishing is on hold until the morning of May 19th.

This PR is ready for merge on May 19th.

#label: "event-triaged-to-10AM"
#label: "missed-content-complete"
#label: “ready-to-merge”

[prmerger-automator]

Are you trying to add/remove a custom label? The syntax for that is #label:"your label".