You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
@dyacob I'm happy for you to make that change. Thanks.
Activity
Spelling and minor grammar corrections as per Issue #129.
dyacob commentedon Oct 17, 2022
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.
r12a commentedon Oct 24, 2022
@dyacob I'm happy for you to make that change. Thanks.