-
Notifications
You must be signed in to change notification settings - Fork 61
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
Correct typos #331
Correct typos #331
Conversation
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.
Thanks! If you have even more typo corrections, perhaps you could collect them in a single commit?
Thank you for your comment. I'm starting to use Eiffel, I'm fixing things down the road.. Maybe we keep this PR open for a while and I'll add new things if address some. |
I'll wait with my approval some time then. @ebram96 , I'm glad you're starting to use Eiffel. If you don't mind it would be great to get some understanding of what use cases you intend to start using Eiffel for. We're always interested to get to know the Eiffel users, to make sure we develop the protocol and its eco-system in the right direction. If you could send a mail to [email protected] we could follow up with you on your specific use cases. And you could also consider joining our mail list and Slack channel, all described here: https://eiffel-community.github.io/community.html. Welcome to the Eiffel community! |
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.
It's been a couple of weeks so I'm going to assume that all typos have been found.
I'll make sure to compose an email when I'm done. |
I think yeah. We can merge this. |
Update glossary.md