fixing SFS service name

Reviewed-by: gtema <artem.goncharov@gmail.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

metadata.yaml

@@ -133,6 +133,23 @@ categories:
         - name: docs-orchestration-rw
           permission: write
       repository: docs/application-operations-management
+    - service_title: Cloud Service Engine
+      service_type: cse
+      docs:
+        - html_location: docs/cse/api-ref
+          rst_location: api-ref/source
+          title: API Reference
+          type: api-ref
+          pdf_name: cse-api-ref
+        - html_location: docs/cse/umn
+          rst_location: umn/source
+          title: User Guide
+          type: umn
+          pdf_name: cse-umn
+      teams:
+        - name: docs-orchestration-rw
+          permission: write
+      repository: docs/cloud-service-engine
     - service_title: Distributed Message Service
       service_type: dms
       docs:
@@ -617,7 +634,7 @@ categories:
         - name: docs-storage-rw
           permission: write
       repository: docs/storage-disaster-recovery-service
-    - service_title: Scalable File System
+    - service_title: Scalable File Service
       service_type: sfs
       docs:
         - html_location: docs/sfs/api-ref

zuul.yaml

@@ -22,6 +22,7 @@
     files:
       - otc_doc_convertor/convertor.py
       - docs/aom
+      - docs/cse
       - docs/dms
       - docs/smn
       - roles