Remove unused anchors in case settings

docs/cases/cases-manage-settings.asciidoc

@@ -16,7 +16,6 @@ image::images/cases-settings.png[Shows the case settings page]
 * <<cases-ui-custom-fields,Add custom fields>>.
 * <<cases-templates,Add templates>>.
 
-[[close-connector]]
 [float]
 [[close-sent-cases]]
 === Case closures
@@ -55,16 +54,12 @@ To create a new connector:
 - {kibana-ref}/swimlane-action-type.html[{swimlane} connector]
 - {kibana-ref}/cases-webhook-action-type.html[{webhook-cm} connector]
 
-[[modify-connector]]
-[[modify-connector-settings]]
 To change the settings of an existing connector:
 
 . Select the required connector from the incident management system list.
 . Click *Update <connector name>*.
 . In the *Edit connector* flyout, modify the connector fields as required, then click *Save & close* to save your changes.
 
-[[default-connector]]
-[[change-default-connector]]
 To change the default connector used to send cases to external systems, select the required connector from the incident management system list.
 
 [float]

docs/serverless/investigate/cases-settings.mdx

@@ -13,17 +13,12 @@ To access case settings in a ((security)) project, go to **Cases** → **Setting
 ![Shows the case settings page](../images/cases-settings/security-cases-settings.png)
 {/* NOTE: This is an autogenerated screenshot. Do not edit it directly. */}
 
-<div id="close-connector"></div>
-<div id="close-sent-cases"></div>
-
 ## Case closures
 
 If you close cases in your external incident management system, the cases will remain open in ((elastic-sec)) until you close them manually.
 
 To close cases when they are sent to an external system, select **Automatically close Security cases when pushing new incident to external system**.
 
-<div id="cases-ui-integrations"></div>
-
 ## External incident management systems
 
 You can push ((elastic-sec)) cases to these third-party systems:
@@ -41,7 +36,6 @@ To push cases, you need to create a connector, which stores the information requ
 To create connectors and send cases to external systems, you need the Security Analytics Complete <DocLink slug="/serverless/elasticsearch/manage-project" text="project feature"/> and the appropriate user role. For more information, refer to <DocLink slug="/serverless/security/cases-requirements">Cases prerequisites</DocLink>.
 </DocCallOut>
 
-<div id="create-new-connector"></div>
 To create a new connector
 
 1. From the **Incident management system** list, select **Add new connector**.
@@ -58,9 +52,6 @@ To create a new connector
     - [((swimlane)) connector](((kibana-ref))/swimlane-action-type.html)
     - [((webhook-cm)) connector](((kibana-ref))/cases-webhook-action-type.html)
 
-<div id="modify-connector"></div>
-<div id="modify-connector-settings"></div>
-
 To change the settings of an existing connector:
 
 1. Select the required connector from the incident management system list.
@@ -69,8 +60,6 @@ To change the settings of an existing connector:
 
 To change the default connector used to send cases to external systems, select the required connector from the incident management system list.
 
-<div id="mapped-case-fields"></div>
-
 ### Mapped case fields
 
 When you export an ((elastic-sec)) case to an external system, case fields are mapped to existing fields in ((sn)), ((jira)), ((ibm-r)), and ((swimlane)). For the ((webhook-cm)) connector, case fields can be mapped to custom or pre-existing fields in the external system you're connecting to.