From 1acd3ab09be1b65bfd6122ee351490c3b5527bb8 Mon Sep 17 00:00:00 2001 From: Alexandre Alapetite Date: Sat, 8 Jan 2022 21:58:55 +0100 Subject: Use typographic quotes (#4133) * Use typographic quotes * A few fixes * Fix * Fix not saved * Implement feedback * Detail * Revert spoken English fixes Left for a future dedicated discussion * More reverts * Final reverts * Final minor --- docs/en/contributing.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'docs/en/contributing.md') diff --git a/docs/en/contributing.md b/docs/en/contributing.md index 62c74b2c2..f18ddda26 100644 --- a/docs/en/contributing.md +++ b/docs/en/contributing.md @@ -1,10 +1,10 @@ ## Report a bug -Have you found a bug? Don't panic, here are some steps to report it with ease: +Have you found a bug? Don’t panic, here are some steps to report it with ease: -1. Search for it on [the bug tracker](https://github.com/FreshRSS/FreshRSS/issues) (don't forget to use the search bar). -2. If you find a similar bug, don't hesitate to post a comment to add more importance to the related ticket. -3. If you didn't find it, [open a new ticket](https://github.com/FreshRSS/FreshRSS/issues/new). +1. Search for it on [the bug tracker](https://github.com/FreshRSS/FreshRSS/issues) (don’t forget to use the search bar). +2. If you find a similar bug, don’t hesitate to post a comment to add more importance to the related ticket. +3. If you didn’t find it, [open a new ticket](https://github.com/FreshRSS/FreshRSS/issues/new). If you have to create a new ticket, please try to keep in mind the following advice: @@ -24,20 +24,20 @@ For a more detailed guide on writing bug reports, please refer to [the in-depth Would you like to fix a bug? For optimum coordination between collaborators, you should follow these indications: -1. Be sure the bug is associated with a ticket and indicate that you'll work on it. +1. Be sure the bug is associated with a ticket and indicate that you’ll work on it. 2. [Fork the project repository](https://help.github.com/articles/fork-a-repo/). 3. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/). The name of the branch should be clear, and ideally prefixed by the related ticket id. For instance, `783-contributing-file` to fix [ticket #783](https://github.com/FreshRSS/FreshRSS/issues/783). 4. Make your changes to your fork and [send a pull request](https://help.github.com/articles/using-pull-requests/). If you have to write code, please follow [our coding style recommendations](developers/02_First_steps.md). -**Tip:** if you're searching for easy-to-fix bugs, please have a look at the "[good first issue](https://github.com/FreshRSS/FreshRSS/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)" ticket label. +**Tip:** if you’re searching for easy-to-fix bugs, please have a look at the “[good first issue](https://github.com/FreshRSS/FreshRSS/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)” ticket label. ## Submit an idea -You have great ideas, yes! Don't be shy and open [a new ticket](https://github.com/FreshRSS/FreshRSS/issues/new) on our bug tracker to ask if we can implement it. The greatest ideas often come from the shyest suggestions! +You have great ideas, yes! Don’t be shy and open [a new ticket](https://github.com/FreshRSS/FreshRSS/issues/new) on our bug tracker to ask if we can implement it. The greatest ideas often come from the shyest suggestions! -If your idea is nice, we'll have a look at it. +If your idea is nice, we’ll have a look at it. ## Contribute to internationalization (i18n) -- cgit v1.2.3