Consistent formatting of references to headers and preferences #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HeikoTheissen
requested changes
Nov 9, 2023
HeikoTheissen
requested changes
Nov 9, 2023
Co-authored-by: Heiko Theißen <[email protected]>
Co-authored-by: Heiko Theißen <[email protected]>
Should the "content-language" be in monospace? Or should the hyphen be deleted? |
…ub.com/oasis-tcs/odata-specs into style/more-consistent-cross-references
Made it monospace everywhere, and adjusted casing. |
…om:oasis-tcs/odata-specs.git into style/more-consistent-cross-references
Should we remove the hyphen here? |
Changed to
|
…ub.com/oasis-tcs/odata-specs into style/more-consistent-cross-references
HeikoTheissen
approved these changes
Nov 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consistently reference headers and preferences