replace rST headers with HTML

Author: bhillmer

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

@@ -1,23 +1,23 @@
 .. _team-dashboard:
 
 ************************************************************************
-Splunk On-Call Team dashboard
+Splunk On-Call 
 ************************************************************************
 
 .. meta::
    :description: Splunk On-Call system requirements, including browsers, mobile support, and incident requirements.
 
 
 
-The Splunk On-Call Team Dashboard provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents. 
+The Splunk On-Call  provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents. 
 
 All incidents derived from integrated monitoring tools in the incident table include  their respective logos to help you rapidly identify the source of an alert. Manually created incidents, along with incidents originating from the Email Endpoint or the REST API integrations, will remain logo free.
 
 Information Alerts can still be found on the Timeline Page.
 
 .. image:: /_images/spoc/team-dashboard.png
     :width: 100%
-    :alt: An image of the team dashboard. On-Call individuals listed on the left; Team incidents are shown in the main pane.
+    :alt: An image of the . 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 team dashboard by selecting :guilabel:`Create Incident` in the top right corner.  For instructions, see :ref:`manual-incident`.
+You can create a manual incident from the  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 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>`. 
+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>`. 
 
 People Table
 ==================

sp-oncall/admin/sso/single-sign-sso.rst

@@ -15,8 +15,11 @@ Configure Single Sign-On for Splunk On-Call
    sp-sso-adfs
    sp-sso-users
 
-Requirements
-==================
+.. raw:: html
+
+  <embed>
+    <h2>Requirements<a name="requirements" class="headerlink" href="#requirements" title="Permalink to this headline">¶</a></h2>
+  </embed>
 
 This integration is compatible with the following versions of Splunk On-Call:
 
@@ -25,18 +28,16 @@ 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>`.
 
-
-
 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
 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
-==========================
+.. raw:: html
+   
+  <embed>
+    <h2>Administrator setup<a name="admin-setup" class="headerlink" href="#admin-setup" title="Permalink to this headline">¶</a></h2>
+  </embed>
 
 Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
 
@@ -46,24 +47,22 @@ Instructions to complete the SSO configuration with Splunk On-Call and your IDP
 - :ref:`sso-azure-spoc`
 - :ref:`sso-aws-spoc`
 
-
-
-.. _sso-onelogin-spoc:
-
-
-OneLogin
--------------
+.. raw:: html
+   
+  <embed>
+    <h3>OneLogin<a name="sso-onelogin-spoc" class="headerlink" href="#sso-onelogin-spoc" title="Permalink to this headline">¶</a></h3>
+  </embed>
 
 If you are configuring SSO for OneLogin, the Default relay state is:
 
    https://portal.victorops.com/auth/sso/<<org-slug-here>>
 
 
-.. _sso-azure-spoc:
-
-
-Azure Active Directory (SAML-based Sign-on)
--------------------------------------------------------
+.. raw:: html
+   
+  <embed>
+    <h3>Azure Active Directory (SAML-based sign-on)<a name="sso-azure-spoc" class="headerlink" href="#sso-azure-spoc" title="Permalink to this headline">¶</a></h3>
+  </embed>
 
 If you are configuring SSO for Azure Active Directory, use the following values:
 
@@ -73,14 +72,14 @@ If you are configuring SSO for Azure Active Directory, use the following values:
 -  Relay State: :samp:`https://portal.victorops.com/auth/sso/<<org-slug-here>>`
 
 
-.. _sso-aws-spoc:
-
-AWS IAM Identity Center - SAML
--------------------------------------------------------
+.. raw:: html
+   
+  <embed>
+    <h3>AWS IAM Identity Center - SAML<a name="sso-aws-spoc" class="headerlink" href="#sso-aws-spoc" title="Permalink to this headline">¶</a></h3>
+  </embed>
 
 If you are configuring SSO for AWS IAM Identity Center:
 
-
 #. In the IAM Identity Center console find the :guilabel:`Applications` tab.
 #.  Select :guilabel:`Add Application` and look for VictorOps.
 #.  In the configuration settings ensure you set the fields as follows: