fix for #9:

- Uniform Intended Audience in respective sections
- typo fixes

doc/OpenSlice_deployment_examples.md

-# OpenSlice deployment examples
+# OpenSlice Deployment Examples
 
 Here are some examples from past and current efforts that use OpenSlice in various cases.
 

doc/architecture/CRIDGE/CRIDGEforDevelopers.md

 
 # CRIDGE: A Service to manage Custom Resources in a Kubernetes Cluster
 
-## Intended Audience: OSL developers
+**Intended Audience: OpenSlice Developers**
  
  >  Kubernetes is an orchestration system for automating software deployment, scaling, and management. One can interact though the Kubernetes API and it has a set of objects ready for use out of the box. Custom Resource Definitions (CRDs) is a way that allows to manage things other than Kubernetes itself and allows to create our own objects The use of CRDs makes the possibilities of Kubernetes management almost limitless. You can extend the base Kubernetes API with any object you like using CRDs.
  

doc/config_intro.md

 # Configuring and managing OpenSlice
 
-## Intended Audience: OpenSlice administrators
+**Intended Audience: OpenSlice Administrators**
 
 This section provides information on how to configure and manage different aspect of OpenSlice while in operation. For example:
 

doc/deployment.md

 # OpenSlice Deployment
 
-This section is meant to guide the user through the installation of OpenSlice. 
+**Intended Audience: OpenSlice Administrators**
 
-## Intended Audience: OpenSlice administrators
+This section is meant to guide the user through the installation of OpenSlice. 
 
 Following, you may thorough guides depending on the installation type of your choice:
 

doc/deploymentCompose.md

 # OpenSlice Deployment Guide with Docker Compose
 
-## Intended Audience: OpenSlice administrators
+**Intended Audience: OpenSlice Administrators**
 
 ## Requirements
 

doc/deploymentK8s.md

 # OpenSlice Deployment Guide with Kubernetes 
 
-## Intended Audience: OpenSlice administrators
+**Intended Audience: OpenSlice Administrators**
 
 ## Requirements
 

doc/etsi_osl.md

-# The ETSI SDG OSL
+# OpenSlice under ETSI
 
-OpenSlice is developed by the OSL ETSI Software Development Group [see more info](https://osl.etsi.org/).
+Since October 2023, OpenSlice has been accepted under the umbrella of ETSI, forming its first Software Development Group (SDG), under the name **ETSI SDG for OpenSlice (OSL)**.
\ No newline at end of file
+
+More information can be found at [ETSI SDG OSL webpage](https://osl.etsi.org/).
\ No newline at end of file

doc/history.md

@@ -2,8 +2,9 @@
 
 * The NFV portal part of OpenSlice was initially developed in H2020 European Research project [5GinFIRE](https://5ginfire.eu) by University of Patras, Greece
 * OpenSlice core services, APIs was further developed and maintained in H2020 European project [5G-VINNI](https://5g-vinni.eu/) by University of Patras, Greece
-* OpenSlice has been a part of OSM's OSS/BSS ecosystem
-* OpenSlice is now an ETSI SDG Group since 2023
+* OpenSlice has been a part of [OSM's OSS/BSS ecosystem](https://osm.etsi.org/wikipub/index.php/OSS_BSS)
+* OpenSlice has been a part of [ETZI ZSM PoC #2](https://zsmwiki.etsi.org/index.php?title=PoC_2_Automated_Network_Slice_Scaling_in_Multi-Site_Environments)
+* OpenSlice is the first ETSI Software Development Group (SDG) since October 2023
 
 
 ## Citation

doc/index.md

+
+# Introduction
+
 <img src="images/openslice_logo.png" alt="logo" width="200"/>
 
 **Version**: 2024Q2 - SNAPSHOT ([Release Notes](https://labs.etsi.org/rep/osl/code/org.etsi.osl.main/-/releases/2024Q2))
@@ -79,9 +82,10 @@ Login credentials:
 * username=admin, password=openslice 
 * username=admin, password=changeme
 
-# Probe further
+## Probe further
 
-* Installing OpenSlice: See the [Deployment](deployment.md) section
+* How OpenSlice works? See the [Architecture](./architecture/architecture.md) section
+* Installing OpenSlice? See the [Deployment](deployment.md) section
 * Learn more on [how OpenSlice supports Network as a Service(NaaS)](./naas/introduction.md)
-* Who is implementing OpenSlice? See [OSL ETSI SDG](https://osl.etsi.org/)
-* How OpenSlice works? See the [Architecture](./architecture/architecture.md) of OpenSlice
+* Who is maintaining OpenSlice? See [OSL ETSI SDG](https://osl.etsi.org/)
+

doc/naas/gst_to_tmf.md

 # Generic Slice Template as a Service Specification
 
-## Intended Audience: Service Designers
+**Intended Audience: OpenSlice Service Designers**
 
 GSMA Generic Slice Template (GST) Defines customer-oriented service requirements, E.g. Availability, Area of service, delay tolerance, etc. and attempts to narrow down the gap between (network) service customers and vendors
 

doc/naas/introduction.md

@@ -2,11 +2,10 @@
 
 This section describes some core concepts for Delivering Network as a Service in OpenSlice. There are many articles and reports on the subject like:
 
-
 * TMF909 API Suite Specification for NaaS
 * TMF926A Connectivity as a Service
-* TMF931-Open Gateway Onboarding and Ordering Component Suite
-* GSMA Open Gatewy initiative
+* GSMA Open Gateway initiative
+* TMF931 Open Gateway Onboarding and Ordering Component Suite
 
 In general Network as a Service (NaaS) is a  service model that allows users to consume network infrastructure and services, similar to how they would consume other cloud services like Software as a Service (SaaS) or Infrastructure as a Service (IaaS). NaaS abstracts the complexity of managing physical network infrastructure, providing users with virtualized network resources that can be dynamically allocated and managed through software.
 

doc/naas/lcm_intro.md

 # Lifecycle Management - LCM
 
-
-Lifecycle Management: The orchestration framework handles the activation, termination and any necessary modifications throughout the service lifecycle.
+**Intended Audience: OpenSlice Service Designers**
 
 
-## Intended Audience: Service Designers
-
+Lifecycle Management: The orchestration framework handles the activation, termination and any necessary modifications throughout the service lifecycle.
 
 In OpenSlice the Lifecycle of a service follows in general the concept of Network Slice lifecycle as defined by 3GPP.
 

doc/naas/lcm_rules_intro.md

 # Lifecycle Management Rules - LCM Rules
 
+**Intended Audience: OpenSlice Service Designers**
 
 Lifecycle Management Rules: Defining complex conditions and actions during the lifecycle of a service and any necessary modifications throughout the service lifecycle.
 
-
-## Intended Audience: Service Designers
-
 OpenSlice end-to-end (E2E) service orchestrator follows some predefined workflows to manage a service lifecycle (They are described in BPMN language and included in our orchestration engine)
 
 So in the system there are already predefined recipes, which in each process-step of the workflow some piece of code is executed. 
@@ -16,7 +14,7 @@ Lifecycle Management Rules: Defining complex conditions and actions during the l
 
 ## How is it possible to intervene in the workflow process and affect it?
 
-LCM Rules are used for defining complex conditions and actions during the lifecycle of a service. In Openslice there are the following types of rules defined:
+LCM Rules are used for defining complex conditions and actions during the lifecycle of a service. In OpenSlice there are the following types of rules defined:
 
 * PRE_PROVISION
 * CREATION

doc/naas/service_catalog.md

 # OpenSlice Service Catalogs
 
-OpenSlice offers complete management of  Service Catalogs.
+**Intended Audience: OpenSlice Service Designers, Administrators, Users**
 
-## Intended Audience: Service Designers, OpenSlice administrators, Users
+OpenSlice offers complete management of Service Catalogs to end users, which comprises:
 
-
-OpenSlice offers complete management of  Service Catalogs which offer to end users:
-
-* Service categories: Lists the available services, including their specifications and performance metrics.
+* Service Categories: Lists the available services, including their specifications and performance metrics.
 * Service Bundles: Combines multiple services into a single offering to provide added value to customers.
 
 Service Catalogs contain Service Specifications (organized in Service Categories) exposed to users for Service Orders.
@@ -15,7 +12,7 @@ Service Catalogs contain Service Specifications (organized in Service Categories
 
 ## UI management
 
-In the UI this looks like the following. Service catalogs and categories exposed in Service marketplace. 
+The UI is built around Service Catalogs and Categories exposed in the Service Marketplace. 
 
 In the menu the administrator can manage the Service Catalogs and Categories.
 

doc/naas/service_inventory.md

 # Service Inventory
 
-Service Inventory contains references to running services that realize a Service Order.
-
-## Intended Audience: Service Designers, OpenSlice administrators, Users
+**Intended Audience: OpenSlice Service Designers, Administrators, Users**
 
+Service Inventory contains references to running services that realize a Service Order.
 
 The Service Inventory is a repository that maintains detailed records of all active services and the underlying resources that support them. It acts as a central repository, tracking the lifecycle of each service from provisioning to decommissioning, and includes references to the specific virtual and physical resources that realize the service, such as servers, network components, storage, and software instances. 
 

doc/naas/service_ordering.md

 # Service Ordering
 
-Customer Facing Service Specifications - or also CFSSpec (organized in Service Categories) are exposed to users for Service Orders.
-
-## Intended Audience: Service Designers, OpenSlice administrators
+**Intended Audience: OpenSlice Service Designers, Administrators**
 
+Customer Facing Service Specifications - or also CFSSpec (organized in Service Categories) are exposed to users for Service Orders.
 
 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. 
 
-Once ACKNOWLEDGED, the service order is processed by OpenSlice orchestration system (OSOM), which schedules/automates the provisioning of the required resources and configurations, coordinating across various components such as MANO controlers for virtual network functions (VNFs), or Containerized controllers  or any 3rd party controllers or services or even physical infrastructure. The OpenSlice orchestration system ensures that all dependencies are managed and that the service is correctly configured.
+Once ACKNOWLEDGED, the service order is processed by OpenSlice orchestration system (OSOM), which schedules/automates the provisioning of the required resources and configurations, coordinating across various components such as MANO controllers for virtual network functions (VNFs), or Containerized controllers  or any 3rd party controllers or services or even physical infrastructure. The OpenSlice orchestration system ensures that all dependencies are managed and that the service is correctly configured.
 
 After provisioning, the service is activated and handed over to the customer, . This end-to-end process ensures a seamless, efficient, and automated delivery of services, enhancing customer satisfaction and operational efficiency.
 

doc/naas/service_spec.md

 # OpenSlice Service Specification
 
-OpenSlice offers complete management of Service Specifications.
+**Intended Audience: OpenSlice Service Designers**
 
-## Intended Audience: Service Designers
+OpenSlice offers complete management of Service Specifications.
 
 Service Specification is an entity that describes a service offering. There are two types of Service Specifications:
 
-* Resource Facing Service Specification
-* Customer Facing Service Specification
+* Resource Facing Service Specification (RFSS)
+* Customer Facing Service Specification (CFSS)
 
 ## Resource Facing Service Specification
 
@@ -55,7 +55,6 @@ endpoint examples:
 /serviceCatalogManagement/v4/serviceSpecification List or find ServiceSpecification objects
 
 
-
 ## Example Use Case
 
 Scenario: A service provider wants to offer a new managed XXXX service to enterprise customers.

doc/naas/so_intro.md

 # Service Orchestration
 
-Definition: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with underlying controller components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers) to provision and configure the required network functions and connectivity.
+**Intended Audience: OpenSlice Service Designers**
+
+*Definition*: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with underlying controller components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers) to provision and configure the required network functions and connectivity.
 
-## Intended Audience: Service Designers
 
 OpenSlice end-to-end (E2E) service orchestration framework is designed to manage and automate the entire lifecycle of services across multiple domains and technologies. For delivering, Network as a Service (NaaS) OpenSlice automates and manages the entire lifecycle of network services, from provisioning to monitoring and decommissioning, while ensuring seamless integration, operation, and delivery of services from the initial request to the final delivery, spanning all involved components and layers.
 

doc/role_keycloak_management.md

 # Role management in Keycloak
 
-Some initial configuration of Keycloak happens at Installation/Deployment time. Here are some notes regarding user management
+**Intended Audience: OpenSlice Administrators**
 
-## Intended Audience: OpenSlice administrators
+Some initial configuration of Keycloak happens at Installation/Deployment time. Here are some notes regarding user management
 
 There are cases that OpenSlice administrators need to configure Keycloak:
 

doc/service_design/examples/ExposingCRDs_aaS_Example_Calculator/ExposingCRDs_aaS_Example_Calculator.md

 
 # Exposing Kubernetes Operators as a Service : Offering "Calculator as a Service" through OpenSlice
 
-## Intended Audience: Service Designers
-
+**Intended Audience: OpenSlice Service Designers**
 
 > To illustrate the powerful concept of Kubernetes operators and how they can be utilized to offer a service through OpenSlice, let's provide an example of a "Calculator as a Service."
 
 > This example will demonstrate the flexibility and capabilities of Kubernetes operators in managing custom resources and automating operational tasks.
 
-
 ---
 ## Offering "Calculator as a Service" through OpenSlice
 
@@ -22,8 +20,7 @@ Assume the following simple CRD of a calculator model accepting two params (spec
 
 The controller (the calculator code) is implemented in any language and is installed in a Kubernetes cluster
 
-```
-
+```yaml
 apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
@@ -66,7 +63,7 @@ spec:
 
 Request to the cluster (through e.g. kubectl apply)
 
-```
+```yaml
 apiVersion: examples.osl.etsi.org/v1alpha1
 kind: MyCalculator
 metadata:
@@ -75,12 +72,11 @@ spec:
   parama: 170
   paramb: 180
   action: 'SUM'
-
 ```
 
 Response
 
-```
+```yaml
 apiVersion: examples.osl.etsi.org/v1alpha1
 kind: MyCalculator
 metadata:
@@ -103,7 +99,7 @@ To perform this through OpenSlice as a Service Specification ready to be ordered
 ---
 ### CRD is saved automatically as Resource Specification
 
-As soon as the CRD is deployed in the cluster (e.g. by your admin via kubctl or via any installation through the internet) it is automatically transformed and is available in OpenSlice catalogs as a Resource Specification.
+As soon as the CRD is deployed in the cluster (e.g. by your admin via kubectl or via any installation through the internet) it is automatically transformed and is available in OpenSlice catalogs as a Resource Specification.
 
 - See also the fully qualified name of the resource specification. 
 	- MyCalculator@examples.osl.etsi.org/v1alpha1@docker-desktop@https://kubernetes.docker.internal:6443/
@@ -122,9 +118,9 @@ As soon as the CRD is deployed in the cluster (e.g. by your admin via kubctl or
 
 
 ---
-# Expose to Users
+## Expose to Users
  
-## Start by Creating a ResourceFacingServiceSpecification
+### Create a ResourceFacingServiceSpecification
 
 From the UI menu create a new Service Specification
 
@@ -135,19 +131,19 @@ From the UI menu create a new Service Specification
 
 
 
-### Creation of CRD-related characteristics
+#### Create CRD-related characteristics
 
 - We need now to adjust some characteristics of this CRD as Resource Specification.
-- OpenSlice transalted automatically the CRD spec in a flat list of characteristics.So the "spec" section from the original yaml for example, is now unfold into: spec, spec.parama, spec.paramb, etc. the same for "status" object
+- OpenSlice translated automatically the CRD spec in a flat list of characteristics.So the "spec" section from the original yaml for example, is now unfold into: spec, spec.parama, spec.paramb, etc. the same for "status" object
 - We need to make OpenSlice aware of when the service will be active.
 	- So we go to characteristic _CR_CHECK_FIELD and we define that the field that shows the status of the service is the characteristic "status.status" (is a text field) 
 	- Then we go to _CR_CHECKVAL_AVAILABLE and we define the value CALCULATED, which signals the following: When the characteristic "status.status" has the value "CALCULATED" then OpenSlice will mark the underlying service as "ACTIVE"
 	- We need also to define the yaml file that OpenSLice will use to create the new resource in the kubernetes cluster
 	- We insert the YAML in the characteristic _CR_SPEC
 	
-	the _CR_SPEC is: 
+The _CR_SPEC is: 
 
-```
+```yaml
 apiVersion: examples.osl.etsi.org/v1alpha1
 kind: MyCalculator
 metadata:
@@ -165,12 +161,12 @@ spec:
 
 > However the values are fixed. How do we allow a user to pass parameters through OpenSlice
 
-## Expose in Catalog
+### Expose in Catalog
 
 Create a new CustomerFacingServiceSpecification
 
 	- Go to the menu Service Specification>New Service Specification
-	- Create a service My Calulator and mark it as a Bundle
+	- Create a service My Calculator and mark it as a Bundle
 	- Go to Service Specification Relationships and add MyCalculatorRFS
 	- The service will be automatically transformed to a "CustomerFacingServiceSpecification"
 	- Add the following characteristics as the image shows:
@@ -192,11 +188,8 @@ We need to Create LCM rules in CustomerFacingServiceSpecification:
 
 ![img12.png](./img12.png)
 
-
-
 If we see one rule it will look like the following:
 
-
 ![img13.png](./img13.png)
 
 - We need to change the _CR_SPEC characteristic of the referenced ResourceFacingServiceSpecification
@@ -206,7 +199,7 @@ If we see one rule it will look like the following:
 - Add a block for text _CR_SPEC 
 - We use a block that changes a String according to variables Text>"A formatted text replacing variables from List"
 - See that we have as Input string the YAML string lines
-	- see that parama, paramb has a %d (they accept integers), action is %s (accepts a string)
+	- See that parama, paramb has a %d (they accept integers), action is %s (accepts a string)
 	- See that the variables tha will replace the %d, %d and %s are an list
 		- the first %d will be replaced with the value from characteristic spec.parama
 		- the second %d will be replaced with the value from characteristic spec.paramb
@@ -237,14 +230,12 @@ Expose it then to a catalogue for orders through the Service Categories and Serv
 
 
 
-### Order the Service
+## Order the Service
 
 When a user orders the service, it will look like this:
 
 ![img16.png](./img16.png)
 
-
-
 - After the Service Order we have 2 services in service inventory on CFS and on RFS. Both have references to values
 - OpenSlice (via CRIDGE service) updates the Resource in Resource Inventory and OSOM updates the Services in Service Inventory
 - The Actual resources are running in the Kubernetes cluster managed by OpenSlice
@@ -256,14 +247,12 @@ When a user orders the service, it will look like this:
 ![img18.png](./img18.png)
 
 
-### Modify the running service
+## Modify the running service
  
 The user can modify the service
  
 ![img19.png](./img19.png)
 
-
- 
 - After a while the update is applied to the cluster, the controller will pick up the resource update and patch the resource
 - OpenSlice (via CRIDGE service) updates the Resource in Resource Inventory and OSOM updates the Services in Service Inventory
 - The result will be available to the respective characteristic "Result" after a few seconds, as need to go through various steps (OpenSlice orchestrator, down to kubernetes, to Calculator controller and back)