Missing Non-functional requirements about performance and storage that are potentially important, for example, the
time taken for each command to execute, the size of the application, and the storage consumed by the storage file.

The definition
Prescription: Uniquely identified by a medication and a start date.
is incorrect as prescription is uniquely identified by medication (medications with the same name are not allowed) and the start date does not uniquely identify the prescription.

The message "Listing all prescriptions that were completed." is confusing because it gives the user the impression that the process is still ongoing, while in reality, it has already been completed. There exists other instances in the application where the past tense is used.
A better message could be to use the past tense, i.e. "Listed all prescriptions that were completed."

When provided with a negative dosage, the system prints the error message "Dosages should only contain numeric characters, and it should not be blank."

This is slightly inaccurate and may cause confusion for the users as the dosage entered is indeed numeric (but negative) and not blank. A better error message should mention that negative dosages are not allowed.

When provided with invalid indices for the edit command, the system returns different error messages.
"Invalid command format" for 0 and negative numbers, "The prescription index provided is invalid" for positive numbers larger than the total number of items. This can potentially be confusing to users.

The "Instructions for Manual Testing" section only consists of 3 parts: Launch and shutdown, Deleting a medication, and Saving data. This is highly incomplete and significantly impedes testing efforts as the reader is not provided with instructions for all (or at least most) of the commands in the application, as shown below:

Instead of printing all the prescription data in one line, the system should have displayed each attribute in one line, otherwise, it significantly affects the readability of the data.

When there are no existing conflicts for an existing drug, and the user enters the listConflict command for a drug, the system prints out "Here are the conflicting drugs." (and no further elaboration).

This is slightly confusing for the user as they are not immediately sure that there are actually no conflicting drugs for this particular drug. A better message could be "There are no conflicting drugs for this drug."

For some long examples in the User Guide, a scrollbar is shown, giving the user the impression that is is scrollable, but the user is unable to scroll with either their mouse or keyboard. This slightly affects the cosmetics of the User Guide.

When using the cfdg/ prefix to add or edit prescriptions in the system, there is no way to validate against any type of user input whatsoever. This could be the source of a lot of bugs due to data entry errors as the application scales. One approach could be to create another model for BayMeds to store valid drugs (with valid names) and check whether the conflicting drugs entered exists in the current list of valid drugs under BayMeds.

Since the folder name is not edited in the code, and the Developer Guide shows the "address", folder, this may be confusing the reader as this application is about medications and there is no mention of address as an input data or name for object.