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

Edited typos in README #16

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Edited typos in README #16

wants to merge 2 commits into from

Conversation

timbolaj
Copy link

@timbolaj timbolaj commented Oct 3, 2020

  • Edited typos in README file.

@timbolaj
Copy link
Author

timbolaj commented Oct 3, 2020

If you choose to accept this PR, would it be possible for you to add the topic of hacktoberfest to this repo? That way, this PR will count towards my contributions.

@igneus
Copy link
Owner

igneus commented Oct 3, 2020

There's no need to add any topic to this repository for your PR to count in Hacktoberfest. See the rules.

@igneus
Copy link
Owner

igneus commented Oct 3, 2020

Regarding the proposed changes: none of the issues you corrected is a mere typo, i.e. an unintentional typing error.

Although I'm a non-native English speaker, well aware of the limits of my language skills, I consider the text as it is (without your changes applied) grammar-wise better than the proposed corrected version. Please prove me wrong if you know I'm not right and want to have the PR merged.

README.md Outdated
@@ -2,16 +2,16 @@

[![Build Status](https://travis-ci.org/igneus/church-calendar-api.svg?branch=master)](https://travis-ci.org/igneus/church-calendar-api)

Browse Roman Catholic liturgical calendar through a web interface
or obtain it's data in JSON format through an API.
Browse the Roman Catholic liturgical calendar through a web interface
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggested the definite article here because it is specific kind of calendar (there is only one liturgical calendar, that which the Vatican has approved).

For ref: https://owl.purdue.edu/owl/general_writing/grammar/using_articles.html#:~:text=The%20definite%20article%20is%20used,the%20dog%20that%20bit%20me.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is only one liturgical calendar, that which the Vatican has approved

There are many Roman Catholic liturgical calendars (General Roman Calendar, calendars of nations, provinces, dioceses, religious orders and their provinces and houses, calendars of single churches, ...) and the API can provide access to many of them, so I'm not sure that the definite article is appropriate here.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah okay, in that case, it should be 'Roman Catholic Liturgical calendars', plural and without the definite article.

Browse Roman Catholic liturgical calendar through a web interface
or obtain it's data in JSON format through an API.
Browse the Roman Catholic liturgical calendar through a web interface
or obtain its data in JSON format through an API.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's is a contraction of the two words 'it is'. Thus the original could be reread as 'or obtain it is data in JSON format through an API'.

Its on the other hand suggests possession/ownership.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is something I've been writing the wrong way my whole life. Thanks.

README.md Outdated

Powered by
[calendarium-romanum][caro] and
grape.

## Explore it on-line
## Explore it online
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only a minor point. Both are legitimate - that said, at least here in Canada, we seldom see it written as 'on-line'

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it's rare nowadays, but I prefer the (now perceived as mildly archaic) dashed form.

README.md Outdated

Church Calendar API is a more or less RESTful read-only JSON API.
Church Calendar API is more or less a RESTful read-only JSON API.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another minor point. Colloquially, the placement of 'a' could come before or after the expression more or less. Rereading it a second time, the only thing I would modify grammar-wise is adding a comma, but I don't think that would be necessary for a README.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I must admit it's been 10+ years since I was subject to thorough English language drills for the last time, so I may be wrong here, but I don't think the meaning of the two text versions is identical:

Church Calendar API is a more or less RESTful read-only JSON API.

Here the adverbs "more or less" modify just the adjective "RESTful", which is exactly what I wanted to say: the RESTful nature of the API could be disputed and I'm aware of that.

Church Calendar API is more or less a RESTful read-only JSON API.

Here the adverbs "more or less" modify the whole expression "RESTful read-only JSON API", which is not what I wanted to say. Church Calendar API is a "read-only JSON API" - not just "more or less", but 100%. It's just "more or less" RESTful.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, then with that context, I withdraw my proposed change for this line.

@timbolaj
Copy link
Author

timbolaj commented Oct 3, 2020

Please see my comments on the commit for explanations on my proposed changes c:

As for the hacktoberfest topic, I had the same thought originally, but when I went on to check my profile, I saw this legend and status update.

Screenshot from 2020-10-03 16-15-17

@igneus
Copy link
Owner

igneus commented Oct 4, 2020

It turns out they recently changed the rules in response to wide criticism, but the change is not yet reflected on the event's website. So I added the "hacktoberfest" topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants