From 518eed2afb2a7969830c9709d20067d50abd66ca Mon Sep 17 00:00:00 2001 From: Kostis Trantzas <ktrantzas@ece.upatras.gr> Date: Thu, 18 Jul 2024 13:22:19 +0300 Subject: [PATCH] minor typo fixes --- doc/naas/service_ordering.md | 4 ++-- doc/service_ordering/ordering_services.md | 4 +++- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/naas/service_ordering.md b/doc/naas/service_ordering.md index 347091d3..29584172 100644 --- a/doc/naas/service_ordering.md +++ b/doc/naas/service_ordering.md @@ -5,7 +5,7 @@ Customer Facing Service Specifications - or also CFSSpec (organized in Service C ## Intended Audience: Service Designers, OpenSlice administrators -The Service Order process is a structured sequence of steps initiated by a customer's Service Order request for a specific service, aimed at delivering and activating the desired service or services (if it is a service bunlde), as well as its related services. It begins with the customer submitting a service request through OpenSlice Services portal or the Service Order API, specifying the necessary details such as service specification, configurations, and any specific requirements. +The Service Order process is a structured sequence of steps initiated by a customer's Service Order request for a specific service, aimed at delivering and activating the desired service or services (if it is a service bundle), as well as its related services. It begins with the customer submitting a service request through OpenSlice Services portal or the Service Order API, specifying the necessary details such as service specification, configurations, and any specific requirements. The request is then validated and verified for completeness and eligibility by an administrator which marks the Service Order as ACKNOWLEDGED otherwise it rejects it. @@ -17,7 +17,7 @@ Ongoing monitoring and other actions can be performed by the Life Cycle manageme <i>***Future developments***: -In future releases it might be possible the ongoing monitoring and support provided to ensure continuous performance and reliability. The service could undergoe a series of tests to ensure it meets the specified performance metrics and SLAs before delivering</i> +In future releases it might be possible the ongoing monitoring and support provided to ensure continuous performance and reliability. The service could undergo a series of tests to ensure it meets the specified performance metrics and SLAs before delivering</i> ## UI management diff --git a/doc/service_ordering/ordering_services.md b/doc/service_ordering/ordering_services.md index 2a09db07..4041aa09 100644 --- a/doc/service_ordering/ordering_services.md +++ b/doc/service_ordering/ordering_services.md @@ -1,3 +1,5 @@ # Service Ordering -## Intended Audience: Users \ No newline at end of file +## Intended Audience: Users + +_This section is WIP._ \ No newline at end of file -- GitLab