add api design

documentation/API_documentation/Network Slice Booking API Design.md

@@ -13,7 +13,7 @@ Seller: Operator
 
 Mode: Operator provide slice services by NaaS API to enterprise customers directly. 
 
-Example Use Cases: In the past/current, most of  current slice customer need to order slice from operators directly through operator customer managemer. This takes time from 2 weeks to 2 month. Those kind of customers may renew, reopen, modify, close the slice service using NaaS Slice APIs. 
+Example Use Cases: In the past/current, most of current slice customer need to order slice from operators directly through operator customer managemer. This takes time from 2 weeks to 2 month. Those kind of customers may renew, reopen, modify, close the slice service using NaaS Slice APIs. 
 
 
 
@@ -38,6 +38,7 @@ Step3: Provider provide the slice to the individuals (to C) directly.
 
 
 
+
 3. Scenario3 - B2B2C
 
    OTT buy the slice, and resell the slice. 
@@ -67,6 +68,7 @@ Basically there should be a CRUD for "Reserve a Slice Resource" and a CRUD for "
     - For those who would like to activate devices within 1 click, may provide the end devices infos. 
     - For those who would like to later activate devices, or don't know which devices to active when order the slice resource, may later call API2 to do activation. Suitable for B2B2C scenario.
 
+
 - API 2：Manage the access control of devices to the slice
 - Function:
   - Slice Owners may have the right to allow access of devices to slice between the time of the order been made till the services ends.