More context required please

[Function-10]

• "Specifies the destination prefix of the route to add." does not tell me why & when I would want to use the "-DestinationPrefix" option. What effect does this have on the VPN connection?
• "Specifies the metric of the route being added to the VPN connection" does not tell me why & when I would want to use the "-RouteMetric" option. What effect does this have on the VPN connection?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 59b602a8-0420-adf8-bc2c-116a336fc37f
• Version Independent ID: ac7c834d-81d1-30f9-951e-36bc3a30aaaa
• Content: Add-VpnConnectionRoute (vpnclient)
• Content Source: docset/windows/vpnclient/Add-VpnConnectionRoute.md
• Product: w10
• Technology: powershell-windows
• GitHub Login: @AndreaBarr
• Microsoft Alias: v-anbarr

[o0nj]

@Function-10

The issue has been noted and the document will be revised in the light of your feedback.

Thank you.

[mikenor]

Honestly, explaining routing table entries is way beyond the scope of this cmdlet documentation, IMO. Both of those parameters should be of obvious purpose to anybody who is adding entries to the routing table. If you don't know why or when you would modify the routing table, the help for the cmdlet to modify the routing table probably isn't the best place to start.

[Function-10]

Honestly, explaining routing table entries is way beyond the scope of this cmdlet documentation,

The rule of definition is that the definition of any word X may not include the word X that is being defined. Quora
The nine word sentence for the parameter does not give an indication of the impact & change of behaviour caused when using it. This is the online help, the expanded version of what you get on the command line.

IMO. Both of those parameters should be of obvious purpose to anybody

The concept of common sense is a long-standing term, based on human experience and people's individual perceptions. Common sense isn't actually common, in either sense: it is different from person to person, and may not be employed even when many editors could agree on what it is in a particular situation.
Thus, when discussing issues of importance to projects on Wikipedia, don't consider your position, or the position that you agree with, or even a position that has consensus, to be "common sense", because it's nothing more than your perception. Your idea of common sense is likely to contradict someone else's idea of common sense
Wikipedia:Common sense is not common

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!