More representative examples in user guide: section on editing Events

[w-yeehong]

Expected Outcome

Section on Editing an event should have examples that contain more recent dates & ideally different dates too.

Description

Examples for this section only use 23-10-1234 12:30 as the date and time.

[nus-se-bot]

Team's Response

Not a documentation bug. Example has no error and is easily understood.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Hello, thank you for your response.

I understand that there is no error in the example. What I am concerned about is whether the example chosen in the guide is representative and clear to the user. Shouldn't an example try to showcase a command that the intended users would usually execute? This includes the parameters for the commands too. 1234 may not seem like a year from some years' perspective and can confuse them. Wouldn't it be better to use another year, perhaps 2016, which is more indicative that it is a year and probably more helpful for the users?

I do think the severity can be changed to VeryLow though.

---