-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: change relavent to relevant (typo fix) #11230
Conversation
There is a typo on line 578 that is being corrected with this change.
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions. |
@georgewrmarshall @DDDDDanica is this something the pixel police team could help me with? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice work @coreyjanssen! 👢🐛 🚀
e7f2b93
Quality Gate passedIssues Measures |
There is a typo on line 578 that is being corrected with this change.
Description
This is a fix for a typo on line 578 (relevant was misspelled as relavent). It appears on the MetaMetrics opt in screen. Doesn't seem to be an issue in Extension, Mobile only.
Related issues
Fixes: #11227
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist