-
Notifications
You must be signed in to change notification settings - Fork 4
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
Possible typo #129
Comments
Agree, and thanks for pointing this out @xfq. While fixing this typo I addressed a number of others that a spellchecker illuminated, and have committed the corrections. One thing I notice now in the document is the use of "Sebatbeit" which was the Unicode term in use since v4.1 (2004). The current, more inclusive preferred term, would be "Gurage" which Unicode v14 uses (2021). So an update to replace "Sebatbeit" with "Gurage" would be advised. @r12a , if you concur I am happy to proceed. Note: I initially committed and pushed with a message that referenced the wrong issue number, I corrected with "git --amend". When pushing after amend, less than a minute later, git told me that my local branch was now behind the remote. So I had to pull and merge to then make the push. This may look odd in the commit history, it doesn't appear that the merge touched any files. |
@dyacob I'm happy for you to make that change. Thanks. |
https://www.w3.org/International/elreq/#how_developed
"philogy" should probably be "philology" here?
The text was updated successfully, but these errors were encountered: