Update cd2dbrush-class.md

[ocucu]

Replaced 'render target' with 'brush' in the CD2DBrush::SetTransform function description

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit a8d51bc:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/mfc/reference/cd2dbrush-class.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 5db2e8b:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/mfc/reference/cd2dbrush-class.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

[Court72]

@TylerMSFT

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

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

[TylerMSFT]

Thank you for updating this, @ocucu

[learn-build-service-prod]

Learn Build status updates of commit 3a2b714:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/mfc/reference/cd2dbrush-class.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

[Court72]

@ocucu - Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, we can move forward with your pull request. Thanks!

[TylerMSFT]

Hey @ocucu , we weren't making progress on the CLA, so I ported your changes to the private repo and will publish from there.
I'm closing this since the work is done, and thank you for taking the time to do it.
PR#5110 in the private repo is where I'll publish your changes from.
Thank you.