Update link to general docs on spaces

This link will be broken until elastic/docs-content#55 is merged

docs/serverless/security-spaces.mdx

@@ -5,9 +5,7 @@ description: Learn how spaces work in ((elastic-sec)).
 tags: [ 'serverless', 'security', 'reference' ]
 ---
 
-{/* TO DO: Replace link below (which points to ESS docs) with page in serverless general docs (once it's added). */}
-
-((elastic-sec)) supports the organization of your security operations into logical instances with the [spaces](((kibana-ref))/xpack-spaces.html) feature. Each space in ((kib)) represents a separate logical instance of ((elastic-sec)) in which detection rules, rule exceptions, value lists, alerts, Timelines, cases, and ((kib)) advanced settings are private to the space and accessible only by users that have role privileges to access the space. For details about configuring privileges for ((es)) and ((kib)), refer to <DocLink slug="/serverless/security/detections-requirements" section="detections-permissions-section" />.
+((elastic-sec)) supports the organization of your security operations into logical instances with the <DocLink slug="/serverless/spaces">spaces</DocLink> feature. Each space in ((kib)) represents a separate logical instance of ((elastic-sec)) in which detection rules, rule exceptions, value lists, alerts, Timelines, cases, and ((kib)) advanced settings are private to the space and accessible only by users that have role privileges to access the space. For details about configuring privileges for ((es)) and ((kib)), refer to <DocLink slug="/serverless/security/detections-requirements" section="detections-permissions-section" />.
 
 For example, if you create a `SOC_prod` space in which you load and activate all the ((elastic-sec)) prebuilt detection rules, these rules and any detection alerts they generate will be accessible only when visiting the ((security-app)) in the `SOC_prod` space. If you then create a new `SOC_dev` space, you'll notice that no detection rules or alerts are present. Any rules subsequently loaded or created here will be private to the `SOC_dev` space, and they will run independently of those in the `SOC_prod` space.