Fix mismatched option code in example in Add-DhcpServerv6OptionDefinition.md

[dodexahedron]

Changed one character:

The option code used in the example does not match the IANA registered code for that option name.

See the official IANA number assignments here:
https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#table-dhcpv6-parameters-2

If someone were to actually run that example as-is, invalid data would be served for a different option that has a very different format, no matter what they configured as the value for the option.

Option 36 is for civic geolocation data.
The example is talking about the BCMCS address option, which is 34.

PR Summary

• Changed the mismatched option code 36 to 34 for the example, to match the rest of the example and explanation.

PR Checklist

• Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• Summary: This PR's summary describes the scope and intent of the change.
• Contributor's Guide: I have read the [contributors guide][contrib].
• Style: This PR adheres to the [style guide][style].

CLA previously signed.

R2G.

[learn-build-service-prod]

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]

Learn Build status updates of commit 3a7b6b5:

✅ Validation status: passed

File	Status	Preview URL	Details
docset/winserver2025-ps/DhcpServer/Add-DhcpServerv6OptionDefinition.md	✅Succeeded	View (WindowsServer2025-ps)

For more details, please refer to the build report.