x-team
diff --git a/‎.github/PULL_REQUEST_TEMPLATE.md
+2-4 b/‎.github/PULL_REQUEST_TEMPLATE.md
+2-4
diff --git a/‎lib/all.js
+12-12 b/‎lib/all.js
+12-12
diff --git a/‎lib/all.js.map
+1-1 b/‎lib/all.js.map
+1-1
diff --git a/‎lib/editor.js
+2-2 b/‎lib/editor.js
+2-2
diff --git a/‎lib/editor.js.map
+1-1 b/‎lib/editor.js.map
+1-1
diff --git a/‎lib/fonts.js
+1-1 b/‎lib/fonts.js
+1-1
diff --git a/‎lib/fonts.js.map
+1-1 b/‎lib/fonts.js.map
+1-1
diff --git a/‎lib/registration.js
+9-2 b/‎lib/registration.js
+9-2
diff --git a/‎lib/registration.js.map
+1-1 b/‎lib/registration.js.map
+1-1
@@ -26,21 +26,19 @@ Fixes https://x-team-internal.atlassian.net/browse/XP-__ISSUE_NUMBER__
 
 ## Checklist
 
-**Before submitting a pull request,** please make sure the following is done:
+**Before submitting a Pull Request,** please make sure the following is done:
 
-<!-- Remove items that do not apply. Just tick completed items in UI -->
+<!-- Remove items that do not apply and tick completed items in UI -->
 - [ ] set yourself as an assignee
 - [ ] set appropriate labels for a PR (`In Review` or `In Progress` depending on its status)
 - [ ] move respective JIRA issue to the `PEER REVIEW` column
-- [ ] make sure your code lints (`npm run lint`)
 - [ ] Flow typechecks passed (`npm run flow`)
 - [x] Snapshots tests passed (`npm run jest`) (**NOTE:** This is temporarily disabled. Skip it.)
 - [ ] check cleanup tasks (https://github.com/x-team/xp/labels/cleanup) and take a suitable small one (if exists) in a related area of the current changes
 - [ ] if added a new UI component that is meant to be used directly by other apps, remember to export that from the appropriate bundle file: `src/index.js` and/or `src/registration.js`
 - [ ] component's documentation (`.stories.js` file) is changed or added accordingly to reflect any new or updated use cases and/or debug cases
 - [ ] if you've fixed a bug, make sure to also include a new story that will expose declarations with problematic data that caused the bug in the first place, so that we can assure that no regressions will pop up on future interactions
 - [x] if any snapshots have been changed, verify that component still works and looks as expected and update the changed snapshot (**NOTE:** This is temporarily disabled. Skip it.)
-- [ ] once finished with all the changes, you run `npm run build` command and committed changed files to the branch
 - [ ] **manually tested the app** by running it in several different browsers (Firefox, Chrome, Opera, Safari, MS IE/Edge, etc.) and checked nothing is broken and operates as expected!
 
 ## Related PRs