Repository navigation
Conversation
|
@dotnet-policy-service agree |
| > from both the [URL specification](https://url.spec.whatwg.org/) and URI | ||
| > [RFC 3986](https://www.rfc-editor.org/rfc/rfc3986.html#section-3.4). | ||
|
|
||
| For example, when embedded in a block of text to be transmitted in a URL, the characters `<` and `>` are encoded as `%3c` and `%3e`. |
There was a problem hiding this comment.
Changing (plus) sign to (plus sign), or in query part of URI to in the query part of a URI seems fine.
The rest - only/either, rewording the last sentence - look worse / less accurate to me.
There was a problem hiding this comment.
Thanks for the review!
I used the wording suggested by the issue author in #13297. I understand your concerns about the technical accuracy of the other changes.
Would you prefer that I keep the original wording and only apply the grammatical corrections you mentioned?
There was a problem hiding this comment.
Thanks! I've updated the note to keep the original technical meaning and applied the grammatical corrections. Could you please take another look?
There was a problem hiding this comment.
Please also revert any unnecessary formatting changes
There was a problem hiding this comment.
Sorry for the unnecessary changes. I've reverted them and kept only the suggested corrections. Thanks for your patience and feedback!
- Reverted unnecessary formatting and wording changes. - Preserved the original technical explanation. - Kept only the grammatical corrections suggested by the reviewer.
Summary
WebUtility.UrlEncodedocumentation using the wording requested in the issue.Fixes #13297
Internal previews
Build report