Remove newlines, indent note under list

doc/user/project/integrations/jira.md

@@ -54,11 +54,10 @@ We have split this stage in steps so it is easier to follow.
 
      ---
 
->**Notes:**
-- Our integration does not support SSO (such as SAML). You will need to create 
-  an HTTP basic authentication password. You can do this by heading to the user 
-  profile, looking up the username, and setting a password.
-
+    NOTE: **Note:**
+    Our integration does not support SSO (such as SAML). You will need to create 
+    an HTTP basic authentication password. You can do this by heading to the user 
+    profile, looking up the username, and setting a password.
 
 1. Now, let's create a `gitlab-developers` group which will have write access
    to projects in JIRA. Go to the **Groups** tab and select **Create group**.
@@ -172,7 +171,7 @@ the same goal:
 
 where `PROJECT-1` is the issue ID of the JIRA project.
 
->**Note:**
+>**Notes:**
 - Only commits and merges into the project's default branch (usually **master**) will
   close an issue in Jira. You can change your projects default branch under
   [project settings](img/jira_project_settings.png).
@@ -230,7 +229,6 @@ Make sure that the JIRA issue is not already marked as resolved, in other words
 the JIRA issue resolution field is not set. (It should not be struck through in
 JIRA lists.)
 
-
 ### CAPTCHA 
 
 CAPTCHA may be triggered after several consecutive failed log in attempts 
@@ -239,7 +237,6 @@ If CAPTCHA has been triggered, you will not be able to use JIRA’s REST API to
 authenticate with the JIRA site. You will need to log in to your JIRA instance
 and complete the CAPTCHA.
 
-
 [services-templates]: services_templates.md
 [jira-repo-old-docs]: https://gitlab.com/gitlab-org/gitlab-ce/blob/8-13-stable/doc/project_services/jira.md
 [jira]: https://www.atlassian.com/software/jira