Public-Mesh-Research-Report.md

@@ -333,18 +333,15 @@ In order to support multi-device scenarios, we developed the "allocator characte
 
 In more detail, the allocator characteristic system uses the following characteristics:
 
-- Array of Read Characteristics
-
+- **Array of Read Characteristics:**
 Each element of this array is a characteristic that a single central will read data from.
 The number of read characteristics is defined when the peripheral starts its GATT service, based on the number of simultaneous central connections the peripheral can support, or a hardcoded value if the number of supported connections isn't known.
 
--   Allocator Characteristic
-
+- **Allocator Characteristic:**
 This is a read characteristic that contains a list of values, each of which is either a null value or the session identifier of a connected central.
 The elements of this list correspond to the elements of the array of read characteristics: a null value means the corresponding read characteristic is unallocated, while a non-null value means the corresponding read characteristic is allocated to the central with the given session identifier.
 
--   Write Characteristic
-
+- **Write Characteristic:**
 All connected centrals write to the same characteristic.
 The peripheral can tell which central is the source of each write, so there's no need for an array of write characteristics.