Update spelling section #2
Merged
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
|
👋 Since this is a community submitted pull request, a Buildkite build has not been started automatically. Would an Elastic organization member please verify the contents of this pull request and kick off a build manually? |
mdbirnstiehl
approved these changes
May 24, 2024
Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: Mike Birnstiehl <[email protected]>
| | defense | defence | | ||
| | pretense | pretence | | ||
|
|
||
| ## Nouns that end with 'og' or 'ogue' |
There was a problem hiding this comment.
Just noticed that there's a small typo here I'll need to fix. It should be:
Nouns that end with og
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.
Rewrote and expanded on existing spelling guidelines for UI copy. Some of the changes I made: