[Docs] Remove first person "I" from Getting started #27155
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
When reading the getting started tutorial I was occasionally confused by the occurence of a first person "I" that was refered to as if in a blog post, but it is unclear who is talking here. I think it would be better to avoid this style and switch to an unpersonal style in the reference.
cbuescher
changed the title
|
@javanna thanks for the review |
cbuescher
added a commit
that referenced
this pull request
Oct 30, 2017
Avoid first person style and consistently switch to an unpersonal style in the getting started docs.
cbuescher
added a commit
that referenced
this pull request
Oct 30, 2017
Avoid first person style and consistently switch to an unpersonal style in the getting started docs.
cbuescher
added a commit
that referenced
this pull request
Oct 30, 2017
Avoid first person style and consistently switch to an unpersonal style in the getting started docs.
jasontedor
added a commit
to olcbean/elasticsearch
that referenced
this pull request
Oct 30, 2017
* master: (63 commits) [Docs] Fix note in bucket_selector [Docs] Fix indentation of examples (elastic#27168) [Docs] Clarify `span_not` query behavior for non-overlapping matches (elastic#27150) [Docs] Remove first person "I" from getting started (elastic#27155) [Docs] Correct link target for datatype murmur3 (elastic#27143) Fix division by zero in phrase suggester that causes assertion to fail Enable Docstats with totalSizeInBytes for 6.1.0 Adds average document size to DocsStats (elastic#27117) Upgrade Painless from ANTLR 4.5.1-1 to ANTLR 4.5.3. (elastic#27153) Exists template needs a template name (elastic#25988) [Tests] Fix occasional test failure due to two random values being the same Fix beidermorse phonetic token filter for unspecified `languageset` (elastic#27112) Fix max score tracking with field collapsing (elastic#27122) [Doc] Add Ingest CSV Processor Plugin to plugin as a community plugin (elastic#27105) Removed the beta tag from cross-cluster search fixed typo in ConstructingObjectParse (elastic#27129) Allow for the Painless Definition to have multiple instances (elastic#27096) Apply missing request options to the expand phase (elastic#27118) Only pull SegmentReader once in getSegmentInfo (elastic#27121) Fix BWC for discovery stats ...
jasontedor
added a commit
that referenced
this pull request
Oct 30, 2017
* master: Refactor internal engine [Docs] #26541: add warning regarding the limit on the number of fields that can be queried at once in the multi_match query. [Docs] Fix note in bucket_selector [Docs] Fix indentation of examples (#27168) [Docs] Clarify `span_not` query behavior for non-overlapping matches (#27150) [Docs] Remove first person "I" from getting started (#27155)
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.
When reading the getting started tutorial I was occasionally confused by the
occurence of a first person "I" that was refered to as if in a blog post, but it
is unclear who is talking here. I think it would be better to avoid this style
and switch to an unpersonal style in the reference.