Fix links: targets from stateful to serverless

Author: joepeeples

docs/serverless/explore/data-views-in-sec.mdx

@@ -46,14 +46,6 @@ This only allows you to add index patterns that match indices that currently con
 
 The default ((data-source)) is defined by the `securitySolution:defaultIndex` setting, which you can modify in <DocLink slug="/serverless/security/advanced-settings">advanced settings</DocLink>.
 
-The first time a user visits ((elastic-sec)) within a given ((kib)) [space](((kibana-ref))/xpack-spaces.html), the default ((data-source)) generates in that space and becomes active.
-
-{/* Feature visibility is not available in serverless. Omitting this note for now, but keeping it commented out just in case someone decides to add feature visibility to serverless later.
-
-TO-DO: in the first sentence of the following note, link to the Serverless page that explains feature visibility. */}
-
-{/* <DocCallOut title="Note">
-    Your space must have **Data View Management** {kibana-ref}/xpack-spaces.html#spaces-control-feature-visibility[feature visibility] feature visibility setting enabled for the default ((data-source)) to generate and become active in your space. 
-</DocCallOut> */}
+The first time a user visits ((elastic-sec)) within a given ((kib)) <DocLink slug="/serverless/spaces">space</DocLink>, the default ((data-source)) generates in that space and becomes active.
 
 If you delete the active ((data-source)) when there are no other defined ((data-sources)), the default ((data-source)) will regenerate and become active upon refreshing any ((elastic-sec)) page in the space.

docs/serverless/sec-requirements.mdx

@@ -18,7 +18,7 @@ supported operating systems, platforms, and browsers on which components such as
 
     To use ((elastic-sec)), your role must have at least:
 
-    * `Read` privilege for the `Security` feature in the [space](((kibana-ref))/xpack-spaces.html). This grants you `Read` access to all features in ((elastic-sec)) except cases. You need additional <DocLink slug="/serverless/security/cases-requirements">minimum privileges</DocLink> to use cases.
+    * `Read` privilege for the `Security` feature in the <DocLink slug="/serverless/spaces">space</DocLink>. This grants you `Read` access to all features in ((elastic-sec)) except cases. You need additional <DocLink slug="/serverless/security/cases-requirements">minimum privileges</DocLink> to use cases.
     * `Read` and `view_index_metadata` privileges for all ((elastic-sec)) indices, such as
     `filebeat-*`, `packetbeat-*`, `logs-*`, and `endgame-*` indices.