more changes from conversion

Author: bhillmer

sp-oncall/admin/get-started/team-dashboard.rst

@@ -17,7 +17,7 @@ Information Alerts can still be found on the Timeline Page.
 
 .. image:: /_images/spoc/team-dashboard.png
     :width: 100%
-    :alt: An image of the . On-Call individuals listed on the left; Team incidents are shown in the main pane.
+    :alt: An image of the team dashboard On-Call individuals listed on the left; Team incidents are shown in the main pane.
 
 
 Filters
@@ -44,12 +44,12 @@ Quickly identify responsible parties during a firefight by easily seeing which p
 Manual Incident Creation
 ----------------------------
 
-You can create a manual incident from the  by selecting :guilabel:`Create Incident` in the top right corner.  For instructions, see :ref:`manual-incident`.
+You can create a manual incident from the team dashboard by selecting :guilabel:`Create Incident` in the top right corner. For instructions, see :ref:`manual-incident`.
 
 Incident War Rooms
 ----------------------------
 
-Access Incident Details directly from the  by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`. 
+Access Incident Details directly from the team dashboard by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`. 
 
 People Table
 ==================

sp-oncall/admin/sso/sp-sso-adfs.rst

@@ -7,45 +7,28 @@ Configure Active Directory Federation Services Single Sign-On for Splunk On-Call
 .. meta::
    :description: Enable Splunk On-Call SSO for Active Directory Federation Services (ADFS) your organization. 
 
-
-
-
 Requirements
 ==================
 
 This integration is compatible with the following versions of Splunk On-Call:
 
 - Full-Stack
 
-To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
-interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
-
-
+To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
 
-Configure Single Sign On (SSO) between your Identity Provider (IDP) and  Splunk On-Call. Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
+Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
 complete the setup on the back-end and respond with confirmation.
 
 If your IDP does not have SAML capability, please contact Splunk On-Call Support to explore what alternative options may be available. For details on how to contact Splunk On-Call Support, see :ref:`spoc-support`.
 
-
-Administrator Setup
-==========================
-
-Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
-
-- :ref:`sso-okta-spoc`
-- :ref:`sso-google-spoc`
-- :ref:`sso-onelogin-spoc`
-- :ref:`sso-adfs-ac-spoc`
-
-
 .. _sso-adfs-ac-spoc:
 
+Configure SSO for Active Directory Federation Services (ADFS)
+==============================================================
 
-Active Directory Federation Services (ADFS)
-===========================================================
+To configure SSO for Splunk On-Call using ADFS complete the following steps.
 
-Once you have sent over your Metadata file, and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
+#. Once you have sent over your Metadata file and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
 
 #. In the ADFS Management console, navigate to :guilabel:`Trust Relationships`, then :guilabel:`Relying Party Trusts` and select :guilabel:`Add Relying Party Trust` in the :menuselection:`Actions` pane.
 

sp-oncall/admin/sso/sp-sso-google.rst

@@ -7,7 +7,7 @@ Configure Single Sign-On for Splunk On-Call using Google Apps
 .. meta::
    :description: Enable Splunk On-Call SSO for your organization. 
 
-To configure SSO for Splunk On-Call using Google Apps:
+To configure SSO for Splunk On-Call using Google Apps complete the following steps.
 
 #. Access the Admin portal for Google Apps and navigate to :guilabel:`Apps` then :guilabel:`SAML Apps`.
 

sp-oncall/admin/sso/sp-sso-okta.rst

@@ -7,9 +7,6 @@ Configure Single Sign-On for Okta and Splunk On-Call
 .. meta::
    :description: Enable Splunk On-Call SSO for your organization. 
 
-
-
-
 Requirements
 ==================
 
@@ -20,20 +17,10 @@ This integration is compatible with the following versions of Splunk On-Call:
 To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
 interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
 
-
-Administrator Setup
+Configure SSO for Okta
 ==========================
 
-Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
-
-- :ref:`sso-okta-spoc-setup`
-- :ref:`sso-google-spoc`
-- 
-
-.. _sso-okta-spoc-setup:
-
-Okta
-==========
+To configure SSO for Okta complete the following steps.
 
 #. From the Okta user homepage, select :guilabel:`Admin` to access the Okta Admin dashboard.
 

sp-oncall/alerts/team-escalation-policy.rst

@@ -11,7 +11,7 @@ Escalation policies determine set who is actually on-call for a given team and a
 
 Some things to note:
 
-- Only Team and Global Admins are able to make changes to Escalation Policies
+- Only Team and Global Admins are able to make changes to Escalation Policies.
 - Only users specified in the first step of an Escalation Policy will receive Timeline and Push notifications that they are on-call and will log hours in the on-call report as being on-call. If you would like users in subsequent steps of an escalation policy to receive these notifications and log these hours, see :ref:`multi-escalation-policies`.
 - When an Escalation Policy is executed and a user is being notified, the user's personal paging policy determines how they will be contacted. See :ref:`custom-paging-policy`.