Usage of [-] in UG is unclear

[fungg0]

Multiple times [-] appeared in expected output, while during the actual program, there is a number. It is quite confusing as [-] is not addressed in the UG, while the number that shows up in the program is not explained also.

For example I obtain 1.22, but I do not know what it is affected by.

[nus-pe-script]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Cover range

I don't understand entirely what this means. It would be nice if it was explained somewhere, in the UG or in the gameplay

---

_{[original: nus-cs2113-AY2324S2/pe-interim#2239] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

We think it should be a documentation bug as we missed the explanation in the UG.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• [x] I disagree

Reason for disagreement: This issue is not talking about the AFTER SAVE ANALYSIS being undocumented, but rather the usage of [-] in the UG.

As [-] is used in the "expected outcome" of the UG, I should have seen [-] in the program, but I did not. This can be sort of circumvented by putting a disclaimer afterwards, yet it was totally not addressed at all.

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The issue of using [-] is done several times throughout the UG for several different expected outputs (more than 3). As such, user will very likely encounter the symbol and can result in questions with regards to what should actually be seen or interpreted for the output. Thus, I think this issue should be Medium rather than Low.

---