GitBook: [main] 56 pages and 22 assets modified

tutorials_tutorials/add-your-own-builtin.md

@@ -27,11 +27,11 @@ mkdir my-new-super-service
 cd new-super-service
 ```
 
- Replace _my_-_new-super-service_ with your service name. 
+Replace _my_-_new-super-service_ with your service name.
 
 Now we can build and populate the required directory structure with your service assets. You should put your service files in the corresponding _my_-_new-super-service_ directory.
 
-### Requirements
+## Requirements
 
 In order to deploy a builtin service, we need
 
@@ -39,7 +39,7 @@ In order to deploy a builtin service, we need
 * the blueprint file for the service
 * the optional start and scheduling scripts
 
-#### Blueprint
+### Blueprint
 
 Blueprints capture the service name and dependencies:
 
@@ -73,7 +73,7 @@ b3sum my_module_3.wasm
 
 If you decide to use the hash approach, please use the hash for the config files names as well \(see below\).
 
-#### **Start Script**
+### **Start Script**
 
 Start scripts, which are optional, execute once after service deployment or node restarts and are submitted as _air_ files and may be accompanied by a _json_ file containing the necessary parameters.
 
@@ -95,11 +95,11 @@ and the associated data file:
 }
 ```
 
-#### **Scheduling Script**
+### **Scheduling Script**
 
 Scheduling scripts allow us to decouple service execution from the client and instead can rely on a cron-like scheduler running on a node to trigger our service\(s\). For a brief overview, see [additional concepts](../development_development/development_reward_block_app/development_additional_concepts.md)
 
-#### Directory Structure
+### Directory Structure
 
 Now that we got our requirements covered, we can populate the directory structure we started to lay out at the beginning of this section. As mentioned above, service deployment as a builtin is an automated workflow one our PR is accepted. Hence, it is imperative to adhere to the directory structure below: