Fix a typo in a newly-introduced string for 20.1 #16749
Merged
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.
What
@tobifjellner spotted a typo in a newly-introduced string in WPAndroid 20.1 and reported it to us here in the WPorg slack
This PR simply fixes the typo so it gets re-imported into GlotPress.
How
WordPress/src/main/res/values/strings.xmlbundle exec fastlane update_frozen_strings_for_translationso that the typo gets included in the frozen strings file that are imported by GlotPress (fastlane/resources/values/strings.xml) via cronℹ️ This PR targets the
release/20.1since this typo fix will have to be included in the next 20.1 beta and final release.Once this PR lands in
release/20.1, I will follow-up with a PR to mergerelease/20.1intotrunkso that the newfastlane/resources/values/strings.xmllands intrunkand gets picked up and re-imported by GlotPressTo test:
Nothing to test, it's just a typo fix. The typo fix will ship in the next beta that we will do later this sprint.