typo fix for best-practice

Reviewed-by: tischrei <tino.schreiber@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

otc_metadata/data/services.yaml

@@ -485,13 +485,13 @@ documents:
     title: API Reference
     type: api-ref
   - environment: internal
-    html_location: docs/ecs/best-practise
-    link: /elastic-cloud-server/best-practise/
-    pdf_name: ecs-best-practise
-    rst_location: doc/best-practise/source
+    html_location: docs/ecs/best-practice
+    link: /elastic-cloud-server/best-practice/
+    pdf_name: ecs-best-practice
+    rst_location: doc/best-practice/source
     service_type: ecs
-    title: Best Practise
-    type: best-practise
+    title: Best Practice
+    type: best-practice
   - hc_location: devg/ecs
     html_location: docs/ecs/dev
     link: /elastic-cloud-server/dev-guide/
@@ -597,13 +597,13 @@ documents:
     title: API Reference
     type: api-ref
   - environment: internal
-    html_location: docs/fg/best-practise
-    link: /function-graph/best-practise/
-    pdf_name: fg-best-practise
-    rst_location: doc/best-practise/source
+    html_location: docs/fg/best-practice
+    link: /function-graph/best-practice/
+    pdf_name: fg-best-practice
+    rst_location: doc/best-practice/source
     service_type: fg
-    title: Best Practise
-    type: best-practise
+    title: Best Practice
+    type: best-practice
   - environment: internal
     html_location: docs/fg/dev
     link: /function-graph/dev-guide/