Control-Plane.md

@@ -12,17 +12,14 @@ To get the switch CLI simply run:
 simple_switch_CLI --thrift-port <port>
 ```
 
-The CLI connect to the Thrift RPC server running in each switch process.
-9090 is the default value but of course if you are running several devices
-on your machine, you will need to provide a different port for each.
-One CLI instance can only connect to one switch device.
+The CLI connect to the *Thrift* server running in each switch process. `9090` is the default value but of course if you are running several devices on your machine, you will need to provide a different port for each. One CLI instance can only connect to one switch device.
 
 #### Filling tables
 
-The most used commands to modify table contents are:
+The most used commands to modify table contents are the following.
 
-  * table_set_default <table_name> <action_name> <action_parameters>
-  * table_add <table_name> <action_name> <match_fields> => <action_parameters>
+- `table_set_default <table_name> <action_name> <action_parameters>` is used to set the default action (i.e. the action executed when no match is found) of a table.
+- `table_add <table_name> <action_name> <match_fields> => <action_parameters>` is used to set the action related to a specific match in a table.
 
 For example if we have the following table:
 
@@ -58,7 +55,7 @@ The first command would set the default action, and action parameters (none in t
 using the `table_name` table if there is no match, the drop action will be called.
 
 In the second example command adds an entry that matches if the `standard_metadata.ingress_port` is equal to 1 and executes the
-action `action_name` with `action_parameter` set to 5.
+action `action_name` with `action_parameter` set to `5`.
 
 #### Writing the CLI input in a file
 
@@ -68,10 +65,10 @@ You can also populate the table writing the commands directly in a text file and
 simple_switch_CLI --thrift-port <port> < command_file.txt
 ```
 
-#### Using P4 utils configuration file
+#### Using *P4-Utils* configuration file
 
-Alternatively, you can use the p4-utils configuration file (i.e `p4app.json`) to set a `cli` configuration
-file for each switch. When creating the topology, or rebooting switches, p4-utils will automatically use
+Alternatively, you can use the *P4-Utils* configuration file (i.e `p4app.json`) to set a `cli` configuration
+file for each switch. When creating the topology, or rebooting switches, *P4-Utils* will automatically use
 the file to populate and configure switches.
 
 To set default `cli` configuration files you need to define your switches like:
@@ -84,10 +81,9 @@ To set default `cli` configuration files you need to define your switches like:
     }
 ```
 
-You can find all the documentation about `p4app.json` in the `p4-utils` [documentation](https://github.com/nsg-ethz/p4-utils#topology-description).
+You can find all the documentation about `p4app.json` in the [*P4-Utils* documentation](https://github.com/nsg-ethz/p4-utils#topology-description).
 
 
-### P4 Utils Control Plane API
+### *P4-Utils* Control Plane API
 
-You can find a wrapper of the Control Plane CLI as one of the features of p4-utils. It basically allows you to do the same but instead of using text sent to
-the CLI you can use the power of a scripting language such as python. You can read more about this API [here](https://github.com/nsg-ethz/p4-utils#control-plane-api).
\ No newline at end of file
+You can find a wrapper of the Control Plane CLI as one of the features of p4-utils. It basically allows you to do the same but instead of using text sent to the CLI you can use the power of a scripting language such as python. You can read more about this API [here](https://github.com/nsg-ethz/p4-utils#control-plane-api).
\ No newline at end of file