From 74acea544f3e75222576915878c6c3ae534aaf15 Mon Sep 17 00:00:00 2001
From: "Hasko, Vladimir" <vladimir.hasko@t-systems.com>
Date: Tue, 4 Jul 2023 22:38:14 +0000
Subject: [PATCH] fixing wrong naming and placement for fg best-practise

Reviewed-by: vladimirhasko <vladimirhasko@gmail.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 | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/otc_metadata/data/services.yaml b/otc_metadata/data/services.yaml
index 570cf88a..abc71ac9 100644
--- a/otc_metadata/data/services.yaml
+++ b/otc_metadata/data/services.yaml
@@ -597,13 +597,13 @@ documents:
     title: API Reference
     type: api-ref
   - environment: internal
-    html_location: docs/fg/best-practice
-    link: /function-graph/best-practice/
-    pdf_name: fg-best-practice
-    rst_location: best-practice/source
+    html_location: docs/fg/best-practise
+    link: /function-graph/best-practise/
+    pdf_name: fg-best-practise
+    rst_location: doc/best-practise/source
     service_type: fg
-    title: Best Practice
-    type: best-practice
+    title: Best Practise
+    type: best-practise
   - environment: internal
     html_location: docs/fg/dev
     link: /function-graph/dev-guide/