From 43f47e0f4aa48a937773e35f0e83de823fba1893 Mon Sep 17 00:00:00 2001 From: Igor Date: Thu, 13 Dec 2018 21:20:34 +0300 Subject: [PATCH] Set apostrophes to uniform style Some apostrophes use more width than they need and all symbols should be in uniform style. --- docs/react/contributing.en-US.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/react/contributing.en-US.md b/docs/react/contributing.en-US.md index d0fc8d859fee..168f0c35b41a 100644 --- a/docs/react/contributing.en-US.md +++ b/docs/react/contributing.en-US.md @@ -36,9 +36,9 @@ Working on your first Pull Request? You can learn how from this free video serie To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/ant-design/ant-design/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) that contain bugs or small features that have a relatively limited scope. This is a great place to get started. -If you decide to fix an issue, please be sure to check the comment thread in case somebody is already working on a fix. If nobody is working on it at the moment, please leave a comment stating that you intend to work on it so other people don’t accidentally duplicate your effort. +If you decide to fix an issue, please be sure to check the comment thread in case somebody is already working on a fix. If nobody is working on it at the moment, please leave a comment stating that you intend to work on it so other people don't accidentally duplicate your effort. -If somebody claims an issue but doesn’t follow up for more than two weeks, it’s fine to take over it but you should still leave a comment. +If somebody claims an issue but doesn't follow up for more than two weeks, it's fine to take over it but you should still leave a comment. ## Sending a Pull Request @@ -48,7 +48,7 @@ The core team is monitoring for pull requests. We will review your pull request 1. Fork the repository and create your branch from [proper branch](#Branch-Organization). 1. Run `npm install` in the repository root. -1. If you’ve fixed a bug or added code that should be tested, add tests! +1. If you've fixed a bug or added code that should be tested, add tests! 1. Ensure the test suite passes (npm run test). Tip: `npm test -- --watch TestName` is helpful in development. 1. Run `npm test -- -u` to update [jest snapshot](http://facebook.github.io/jest/docs/en/snapshot-testing.html#snapshot-testing-with-jest) and commit these changes as well (if has). 1. Make sure your code lints (npm run lint). Tip: Lint runs automatically when you `git commit`.