[incubator-iotdb] branch master updated: Correct typo in Development-Contributing.md. (#649)

[qi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

qiaojialin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-iotdb.git


The following commit(s) were added to refs/heads/master by this push:
     new c50c73f  Correct typo in Development-Contributing.md. (#649)
c50c73f is described below

commit c50c73f84d01e490db58581a09cc079d682d6f86
Author: Jincheng Sun <su...@gmail.com>
AuthorDate: Fri Dec 13 08:57:20 2019 +0800

    Correct typo in Development-Contributing.md. (#649)
---
 docs/Development-Contributing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Development-Contributing.md b/docs/Development-Contributing.md
index f130b7f..24da537 100644
--- a/docs/Development-Contributing.md
+++ b/docs/Development-Contributing.md
@@ -123,7 +123,7 @@ Following `README.md` to test, run or build IoTDB.
 Generally, IoTDB uses JIRA to track logical issues, including bugs and improvements and uses Github pull requests to manage the review and merge specific code changes. That is, JIRAs are used to describe what should be fixed or changed, proposing high-level approaches. Pull requests describe how to implement that change in the project’s source code. For example, major design decisions discussed in JIRA.
 
 1. Find the existing IoTDB JIRA that the change pertains to.
-    1. o not create a new JIRA if you send a PR to address an existing issue labeled in JIRA; add it to the existing discussion.
+    1. Do not create a new JIRA if you send a PR to address an existing issue labeled in JIRA; add it to the existing discussion.
     2. Look for existing pull requests that are linked from the JIRA, to understand if someone is already working on the JIRA
 2. If the change is new, then it usually needs a new JIRA. However, trivial changes, such as changes are self-explained, do not require a JIRA. Example: Fix spelling error in JavaDoc
 3. If required, create a new JIRA: