Information for event in User Guide is Hard to Understand and Lengthy

[WilsonLee2000]

Hi Team, I was unable to understand this paragraph and have to read and re-read multiple times to understand it. This slows down readers of the User Guide.

[soc-se-bot]

Team's Response

We think that it is necessary for the users to understand the concept that the input time will be used recurringly and hence I find it hard to shorten this part. However, it might be the restrictions due to my poor english that I did not explain it very clearly in this chunk of explanation and made it hard for the users to understand. Apologise for that.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Hi Team "However, it might be the restrictions due to my poor english that I did not explain it very clearly in this chunk of explanation and made it hard for the users to understand." As you have acknowledged it yourself, not sure why is this issue still being chosen as response.Rejected.

Nevertheless, as a reader, I am confused with the words and phrases used in that paragraph. For instance, what do you mean by "is less important as the frequency is set as monthly". This was not properly explained in detail. Under your given example of usage, there is no sample example provided for users to understand "the event will always be recorded as a monthly recurring event based on its date." as well.

---