[DOCS] Minor editorial changes to enrich docs

docs/reference/ingest/apis/enrich/execute-enrich-policy.asciidoc

@@ -95,7 +95,7 @@ and deletes the previous enrich index.
 Because this API request performs several operations,
 it may take a while to return a response.
 
-[[sample-api-path-params]]
+[[execute-enrich-policy-api-path-params]]
 ==== {api-path-parms-title}
 
 `<enrich-policy>`::

docs/reference/ingest/apis/enrich/put-enrich-policy.asciidoc

@@ -86,7 +86,7 @@ Instead, you can:
     with the new enrich policy
     in any in-use enrich processors.
 
-.   Use the <<delete-enrich-policy-api, delete enrich policy API>>
+.   Use the <<delete-enrich-policy-api, delete enrich policy>> API
     to delete the previous enrich policy.
 // end::update-enrich-policy[]
 

docs/reference/ingest/enrich.asciidoc

@@ -31,7 +31,7 @@ follow these steps:
 Once you have an enrich processor set up,
 you can <<update-enrich-data,update your enrich data>>
 and <<update-enrich-policies, update your enrich policies>>
-using the <<enrich-apis,enrich APIs>>.
+using the <<enrich-apis,enrich>> APIs.
 
 [IMPORTANT]
 ====
@@ -63,7 +63,7 @@ A *source index* contains data you want to append to incoming documents.
 You can index and manage documents in a source index
 like a regular index.
 
-The following <<docs-index_,index API>> request creates the `users` source index
+The following <<docs-index_,index>> API request creates the `users` source index
 containing user data.
 This request also indexes a new document to the `users` source index.
 
@@ -204,7 +204,7 @@ the processor appends data from those documents to the array.
 If the incoming document matches no documents in the enrich index,
 the processor appends no data.
 
-The following <<docs-index_,Index API>> request uses the ingest pipeline
+The following <<docs-index_,index>> API request uses the ingest pipeline
 to index a document
 containing the `email` field,
 the `match_field` specified in the `users-policy` enrich policy.