diff --git a/kea-multithreading-packet-processing-requirements.md b/kea-multithreading-packet-processing-requirements.md
index f17dbab..3c7bc30 100644
--- a/kea-multithreading-packet-processing-requirements.md
+++ b/kea-multithreading-packet-processing-requirements.md
@@ -3,13 +3,13 @@
 # The initial requirements of the kea multi-threading packet processing design:
 
 1. It must be supported by DHCPv4 and DHCPv6 servers
-* 2 It must not break the DHCP protocol (obviously)
-* 3 It must compile and use supported dependencies on all supported platforms (obviously)
-* 4 It must be configurable in the configuration file, at run-time using control channel commands or on the command line (still in discussion).
-* 5 Should not have impact on the old server functionality if the feature is disabled
-* 6 It must support MySql and PgSql back-ends
-* 7 It must support Memfile and Cassandra back-ends (initial implementation might disable the feature or use a hybrid approach if configured with these back-ends)
-* 8 It must support using hooks (some, all or none) (initial implementation might disable the feature or use a hybrid approach if configured with unsupported hooks)
+2. It must not break the DHCP protocol (obviously)
+3. It must compile and use supported dependencies on all supported platforms (obviously)
+4. It must be configurable in the configuration file, at run-time using control channel commands or on the command line (still in discussion).
+5. Should not have impact on the old server functionality if the feature is disabled
+6. It must support MySql and PgSql back-ends
+7. It must support Memfile and Cassandra back-ends (initial implementation might disable the feature or use a hybrid approach if configured with these back-ends)
+8. It must support using hooks (some, all or none) (initial implementation might disable the feature or use a hybrid approach if configured with unsupported hooks)
 
 ***As the development goes further and the design is perfected, these requirements must be updated.***