Handle weird bugs from PeD

docs/DeveloperGuide.md

@@ -606,6 +606,14 @@ testers are expected to do more *exploratory* testing.
 
 ## **Appendix: Planned Enhancements**
 
+For reference, our group has 5 members.
+
 1. Make `list` command with miscellaneous parameters error message more helpful. Currently, typing `list` with miscellaneous parameters, ex. `list 123`, will result in a message that states "Please ensure your command is valid!". To improve specificity this will be changed to ask user to remove miscellaneous parameters.
 2. Prevent tags from allowing underscores. When searching for tags with underscores in the find command, the underscores are interpreted as an `or`. This means that searching for the tag "low_income" will bring up all tags containing "low" and "income" instead of just "low_income".
-3. Remove `remark` command while keeping remarks. Currently, remarks can be added via the edit command or the remark command but not the add command. Instead of having a dedicated remark command we will allow users to use add command to add remarks while adding a contact and edit command to add or edit the remark of a contact. This change solves an associated issue whereby the remark command currently undoes the detailed view on the contact. 
+3. Remove `remark` command while keeping remark fields. Currently, remarks can be added via the edit command or the remark command but not the add command. Instead of having a dedicated `remark` command, we will allow users to use the `add` command to create a contact with remarks, or the `edit` command to modify the remark of a contact. This change solves an associated issue whereby the remark command currently collapses the detailed view on the contact.
+4. Restrict the validation regex for emails to require at least 2 domain labels in the domainName region of the email. Traditionally, emails require at least 2 domain labels separated by a ., but the current implementation only requires one domain label. Something like johnsmith@yahoo is accepted as an email address when it should be rejected.
+5. Update the error message displayed to the user by the `edit` command upon attempt to index with 0. The current error message for `edit 0 n/Bob` states "invalid command format" when it should mention that the index provided is invalid.
+6. Update the error message displayed to the user by the `remark` command upon attempt to index with 0. The current error message for `remark 0 r/Hates frisbees` states "invalid command format" when it should mention that the index provided is invalid.
+7. Update the error message displayed to the user by the `delete` command upon attempt to index with 0. The current error message for `delete 0` states "invalid command format" when it should mention that the index provided is invalid.
+8. Update the error message displayed to the user by the `view` command upon attempt to index with 0. The current error message for `view 0` states "invalid command format" when it should mention that the index provided is invalid.
+9. Include an example of sorting by date of last visit (`d/`) in the command format message of the `sort` command.

docs/UserGuide.md

@@ -378,3 +378,4 @@ Action     | Format, Examples
 **Seed**   | `seed`
 **Sort**   | `sort PARAMETER_PREFIX/ORDER` <br> e.g., `sort n/ascending`
 **Remark** | `remark INDEX r/REMARK` <br> e.g., `remark 1 r/some remark about contact`
+