#28051 corrected slugs documentation

Author: Grave-Dave

docs/API/content-type/creating-ctd.md

@@ -167,7 +167,6 @@ When you create or update a Content Type Definition with `slugs`:
 * For **active** rules, both `source` and `target` must reference fields that exist
   in the Content Type schema. Otherwise the request returns `400 Bad Request` with
   violations on `slugs[i].source` and/or `slugs[i].target`.
-* `source` and `target` must be different — a rule where they are equal is rejected.
 * For **inactive** rules with missing fields, the rule is silently dropped during
   save — no error is returned, but the rule will not be persisted.
   See the [Content Object documentation](/docs/API/content-type/creating-co/#auto-generated-slug-fields) for details

docs/panel/ContentObjects/slugs.md

@@ -39,8 +39,7 @@ Enabling the switch opens the **Slug settings** modal, where you configure the r
 
 ## Configuring slug rules
 
-In the **Slug settings** modal, each rule is presented as a card (e.g. *Slug #1*) with
-the following controls:
+In the **Slug settings** modal, each rule has the following controls:
 
 ![Slug settings modal](../images/slug-rules/slug-settings-modal.png){: .center .width75 .border}
 
@@ -58,7 +57,7 @@ as usual.
 !!! note
     Both the source and target fields must already exist in the Content Type Definition.
     For an active rule, if either field is missing, saving the definition will fail with a
-    validation error. The source and target must also be two different fields.
+    validation error. The source and target should also be two different fields.
 
 ## How slug generation works