fix jira project key

slawekjaranowski · web-flow · commit 5ab4824ed4f9 · 2022-02-02T19:15:05.000+01:00
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -1,13 +1,13 @@
 Following this checklist to help us incorporate your 
 contribution quickly and easily:
 
- - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed 
+ - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSHARED) filed 
        for the change (usually before you start working on it).  Trivial changes like typos do not 
        require a JIRA issue.  Your pull request should address just this issue, without 
        pulling in other changes.
  - [ ] Each commit in the pull request should have a meaningful subject line and body.
- - [ ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`,
-       where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice
+ - [ ] Format the pull request title like `[MSHARED-XXX] - Fixes bug in ApproximateQuantiles`,
+       where you replace `MSHARED-XXX` with the appropriate JIRA issue. Best practice
        is to use the JIRA issue title in the pull request title and in the first line of the 
        commit message.
  - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
