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

Correcting Typo in README - Updated 'oc' Shortcut to 'oco' Missed in Previous Fix #188

Closed
wants to merge 1 commit into from

Conversation

eitamal
Copy link

@eitamal eitamal commented May 26, 2023

Hello exceptional maintainers! 🚀

I've been having a blast learning and exploring this project and found something minor I could help with.

The README docs had a slight hiccup referring to the renamed shortcut. The document mentions oc in just one more spot where it should be oco. So, I took the liberty of fixing it. No change is too small, right? 😅

The original fix #178, is the one that addressed this and that successfully closed issue #144.

This pull request:

  • Changes the 'oc' shortcut in the README to 'oco', aligning it with the rest of the project as per fix Remove oc alias #178.

Keep up the incredible work, and happy coding! 💻🎉

EDIT: It seems #190 fixes this typo, as well as other errors in the document. So you may as well just go with that pull request instead.

@eitamal
Copy link
Author

eitamal commented May 26, 2023

Just a quick note to add to this pull request for anyone who might be curious:

Before submitting the PR, I wanted to ensure that there were no other instances of the 'oc' typo hanging around. So, I ran rg -w oc in the root directory to verify this was the only 'oc' typo. All clear! 🧹

If you haven't used rg (ripgrep) before, it's a tool similar to grep (but not a replacement). It's blazing fast and ignores patterns from your .gitignore by default.

@di-sukharev
Copy link
Owner

big thanks here <3

lets go with #190 which is almost merged

@eitamal eitamal closed this May 29, 2023
@eitamal eitamal deleted the missed-oc branch May 29, 2023 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants