README.md: Change release to released

[utkarsh2102]

Last line here mentions:

Any code in this repository is to be release under the MIT license.

The word release should be changed to released.

A good newcomer issue.

[ghost]

I’ll do this as well as a proofreading of the readme.

Edit: Now I know that wasn't exactly up to protocol. My bad.

[utkarsh2102]

@shibatan, only work on the issue when you are assigned. Please don't open any unnecessary PRs.

[mnk343]

kindly assign me this issue. i have already requested for the same a few days ago. but still havent got a reply on the coala gitter channel.
thanks

[asrdav]

Hello, please anyone assign to me this issue. It is my first issue

[pavanrkadave]

Hi, I want to work on this issue if no one is assigned to it. This is my first issue.

[asrdav]

Please somebody assign me this issue. I have got the invite and I can make the PR.

[asrdav]

This is my first newcomer issue

[asrdav]

Thanks @li-boxuan

[asrdav]

I am not able to understand the errors. Can someone help?

[shashank-b]

@asrdav, Please check out my comments on your PR.

[asrdav]

Sorry to all the maintainers about the closed PR's.

I have read the commit message guidelines but I could not get the PR correct

[asrdav]

I tried all the headings such as:
1.)Change release to released in README.md
2.)README.md: Change release --> released
3.)Change release to released in README.md

Could anyone tell where should I make the change?

[li-boxuan]

@asrdav I just closed your latest PR and reopened your oldest one. Do not close the old one and open a new one again - you will not be allowed to contribute if you violate the rule again.

If you cannot get the PR correct, ask for help on gitter channel.

[asrdav]

Apology for the mistakes. I won't repeat it again.

…

On Mon, Feb 4, 2019 at 7:41 AM Boxuan Li ***@***.***> wrote: @asrdav <https://github.com/asrdav> I just closed your latest PR and reopened your oldest one. Do not close the old one and open a new one again - you will not be allowed to contribute if you violate the rule again. If you cannot get the PR correct, ask for help on gitter channel. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcUIbypiVPGm3nmqZ_LhKlUtebtuIJeSks5vJ5a2gaJpZM4Y9uF5> .