？？？

docs/DeveloperGuide.adoc

@@ -610,19 +610,19 @@ Moreover, if there is more than one person in the list with the name give, then
 
 ==== Design Considerations
 
-**Aspect:**  Implementation of `DeleteCommandParser`+
+**Aspect:**  Implementation of `DeleteCommandParser` +
 **Alternative 1 (current choice):**  Add a prefix after the command word to distinguish between delete by name or indexes. +
-**Pros:**  It is more convenient to identify the type of input to deal with.+
+**Pros:**  It is more convenient to identify the type of input to deal with. +
 **Cons:**  It is less convenient for users to type in the prefix. +
 **Alternative 2:** Use the type of first input word after command word to differentiate. +
-**Pros:**  It is more convenient for the users to type.+
+**Pros:**  It is more convenient for the users to type. +
 **Cons:** It is harder for the developer to find the type if the users give a name with all numbers to a contact.
 
 ---
 
 **Aspect:**  How to deal with multiple persons with same name condition +
 **Alternative 1 (current choice):**  Do not delete the persons and show all the persons with the same target name on the list. Remind the user to decide which one to delete. +
-**Pros:**  It considers more about the users. Try to ensure the target is the person who the users want to delete.+
+**Pros:**  It considers more about the users. Try to ensure the target is the person who the users want to delete. +
 **Cons:**  It cost users more time to delete a person if they don't know the index of the target. +
 **Alternative 2:** Delete the first person with the name in the list and show it to user. +
 **Pros:**  It cost users less time to delete a person if they know the sequence of the persons with the same name. +