more edits from heretto

Author: bhillmer

sp-oncall/spoc-integrations/jira-app-integration-guide-victorops.rst

@@ -18,17 +18,17 @@ Configure in Splunk On-Call
 Install the Splunk On-Call Add-On in Jira
 ==========================================
 
-#. Log in as a Jira administrator, then select Jira administration gear icon then :guilabel:`Manage apps` to go to the Atlassian Marketplace.
+#. Log in as a Jira administrator, then select the Jira administration gear icon then select :guilabel:`Manage apps` to go to the Atlassian Marketplace.
 #. In the sidebar, select :guilabel:`Find new apps` under the Atlassian Marketplace header.
-#. If you are on Jira Server, search for the app "Splunk On-Call for Jira Server". If you are on Jira Cloud, search for the app "VictorOps for Jira Cloud". After you've located the right app, select :guilabel:`Install`.
+#. If you are on Jira Server, search for the app "Splunk On-Call for Jira Server". If you are on Jira Cloud, search for "VictorOps for Jira Cloud". After you've located the right app, select :guilabel:`Install`.
 #. After installation completes, select :guilabel:`Configure`.
 
 Configuring application settings
 --------------------------------
 
-#. Insert the API key you generated in VictorOps into the :guilabel:`API Key` field under :guilabel:`Connect to your VictorOps Organization` on VictorOps for Jira Server Configuration page.
+#. Enter the API key you generated in VictorOps in the :guilabel:`API Key` field under :guilabel:`Connect to your VictorOps Organization` on the VictorOps for Jira Server Configuration page.
 #. In the :guilabel:`API ID` field in the same section, insert the API ID you coped in the preceding Configure Splunk On-Call step.
-#. Copy the Splunk On-Call org ID displayed in your VictorOps URL. The org ID is at the end of the URL you used to log in: ``https://portal.victorops.com/client/<Org_ID>``. Paste the org ID in Jira's :guilabel:`Organization ID` field.
+#. Copy the Splunk On-Call org ID displayed in your VictorOps URL. The org ID is at the end of the URL you use to log in: ``https://portal.victorops.com/client/<Org_ID>``. Paste the org ID in Jira's :guilabel:`Organization ID` field.
 #. Select :guilabel:`Connect`.
 
 A new entry appears in the Connected VictorOps Organizations section with a green VALID flag.
@@ -38,22 +38,22 @@ A new entry appears in the Connected VictorOps Organizations section with a gree
 Configure Jira project settings
 -------------------------------------
 
-The Splunk On-Call add-on must be enabled and configured for each Jira project you want to associate. While multiple projects can
+The Splunk On-Call add-on must be activated and configured for each Jira project you want to associate. While multiple projects can
 connect to the same Splunk On-Call organization, projects cannot share the same Default Team Escalation Policy.
 
 #. In Jira, select :guilabel:`Projects`.
 #. Go to :guilabel:`Project settings` of the project you want to activate for the Splunk On-Call add-on.
 #. Select :guilabel:`VictorOps Settings`.
 #. Select :guilabel:`Enable VictorOps for this Project`.
 
-The page to displays a list of configurable fields.
+The page displays a list of configurable fields.
 
 Default incident settings
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-#. Under :guilabel:`VictorOps Instance`, select the Splunk On-Call organization you wish to associate with this project.
-#. Under :guilabel:`Default Team Escalation Policy`, select the Splunk On-Call Escalation Policy you would like to page when Jira issues create incidents in Splunk On-Call. Incoming VictorOps incidents assigned to this Escalation Policy are the only incidents allowed to create issues in your Jira project.
-#. Under :guilabel:`Default User`, select the Jira user you wish to designate as reporter for issues generated by incoming Splunk On-Call incidents.
+#. Under :guilabel:`VictorOps Instance`, select the Splunk On-Call organization you want to associate with this project.
+#. Under :guilabel:`Default Team Escalation Policy`, select the Splunk On-Call Escalation Policy you want to page when Jira issues create incidents in Splunk On-Call. Incoming VictorOps incidents assigned to this Escalation Policy are the only incidents allowed to create issues in your Jira project.
+#. Under :guilabel:`Default User`, select the Jira user you want to designate as reporter for issues generated by incoming Splunk On-Call incidents.
 
 Incoming issue settings
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -74,7 +74,7 @@ Define state mapping to allows Jira issues to remain synchronized as incidents m
    :alt: 
    :width: 50%
 
-Create a Splunk On-Call incident within Jira
+Create a Splunk On-Call incident in Jira
 --------------------------------------------------
 
 Splunk On-Call incidents can only be created from the Jira issue view.
@@ -84,7 +84,7 @@ Splunk On-Call incidents can only be created from the Jira issue view.
 #. (Optional) Select a different escalation policy from the :guilabel:`VictorOps Team Escalation Policy` dropdown menu. 
 #. (Optional) Use the :guilabel:`Additional Users` dropdown menu to include additional users for response. Adding users to an incident does not create a multi-responder incident in Splunk On-Call.
 #. Select :guilabel:`Create Incident` to generate a Splunk On-Call incident. A triggered Splunk On-Call incident card displays under the VictorOps section in the issue view.
-#. Select the :guilabel:`Incident Details` in the incident card to display the incident in Splunk On-Call in a new browser tab.
+#. Select the :guilabel:`Incident Details` in the incident card in Splunk On-Call to display the incident in a new browser tab.
 
 .. image:: /_images/spoc/4jira.png
    :alt: