Shorten message on search page #6814
Merged
Conversation
This file contains hidden or 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
Codecov Report
@@ Coverage Diff @@
## master #6814 +/- ##
=======================================
Coverage 84.42% 84.42%
=======================================
Files 266 266
Lines 40474 40474
Branches 5934 5934
=======================================
Hits 34170 34170
Misses 4997 4997
Partials 1307 1307Continue to review full report at Codecov.
|
|
Thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Subject: Shorten message on search page
Purpose
The text was a bit wordy. It's obvious that the search page can be used to search. Also, we don't need to tell people how to use a search field.
The only relevant content of the paragraph is that matches contain all words. That can be described in one concise sentence, which is more likely to be read than a whole paragraph.
Note: This will need translations updates as a follow-up. Should I update the .po files within this PR? It seems these file are not up-to-date anyway and there would be other changes included.