Skip to content
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

πŸ”€ GCXchange spelled incorrectly #12190

Closed
1 task
mnigh opened this issue Dec 4, 2024 · 3 comments Β· Fixed by #12194
Closed
1 task

πŸ”€ GCXchange spelled incorrectly #12190

mnigh opened this issue Dec 4, 2024 · 3 comments Β· Fixed by #12194
Labels
copy Content: What to say and how to say it.

Comments

@mnigh
Copy link
Contributor

mnigh commented Dec 4, 2024

πŸ”€ Copy

GCXchange spelled incorrectly.

πŸ•΅οΈ Details

πŸ™‹β€β™€οΈ Proposed Implementation

Replace GCXCHNAGE with GCXCHANGE.

βœ… Acceptance Criteria

  • no instances of GCXCHNAGE in codebase
@mnigh mnigh added the copy Content: What to say and how to say it. label Dec 4, 2024
@mnigh
Copy link
Contributor Author

mnigh commented Dec 4, 2024

@petertgiles other than the fact that the directive forms have never being published, any reason not to do this?

@petertgiles
Copy link
Contributor

Yeah, it's a typo but it's for a feature that will probably never be released. Doesn't seem like it's worth the time to me. 🀷

@mnigh
Copy link
Contributor Author

mnigh commented Dec 4, 2024

Yeah, it's a typo but it's for a feature that will probably never be released. Doesn't seem like it's worth the time to me. 🀷

Just in case it gets released...😜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
copy Content: What to say and how to say it.
Projects
Status: βœ… Done
Development

Successfully merging a pull request may close this issue.

2 participants