Please can we make it clearer how many Events there are in Scrum?

Four formal events are listed: (page 5)
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective

Then another event is defined (page 9)
- The Sprint (although not as an inspect and adapt event)

Then under the same Scrum Events heading (page 10) we meet:
- Cancelling a Sprint (could it be meant to be seen as an Event?)

Then I have read the argument in this area for one other:
- Product Backlog refinement. Here PBIs are "reviewed and revised" (inspection and adaptation)

I believe it is meant to be 5 Events? But it's hard to be definitive.

First the description then a suggestion below it.
Description:
In the Scrum guide v. Nov-2017. In Scrum Review section the text contains: "This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."

I can't experience any practical effect of the word 'informa meeting'. As English is not my native language, I am not sure if 'informal meeting' has any effect on others. I also asked some coaches,trainers,other scrum masters about what is ment by it. I know the translation of the word, but does it affect our practices? Or does it guide me somewhere?

From the same Scrum guide version: "each event in Scrum is a formal opportunity to inspect and adapt something."

If I combine both, it results in a confusing one: "The informal meeting named Sprint review is a formal opportunity. Sure meeting!=opportunity.

Given that, Sprint review meeting is descibed as "not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
Does descibing it as formal or informal or none of them prior to the above cited sentence affect my sprint review meeting practically?

Additionally, this meetimg is a planned one, has a goal, invitations, room at office place not a restaurant,etc. , which gives it a formal appearance.

Suggestion:
I suggest to change the word 'informal' to ' discussion and decission' or elaborate the original one 'informal'

The change of Product Backlog from prioritised to ordered is actually an error. Priority means "the fact or condition of being regarded or treated as more important than others."

This is what we do with PBs. Whether because of risk, or value, or technology - We always work on the most important first.

Ordered just means "has an order" - In that way we could use scrum and legitimately work on the meaningless nice to haves rather than the key aspects of the product.

This also over empowers the PO role as it means they can decide in totality without interference an order of any type without any reason, where the priority rule in Scrum can help them not commit product suicide by mistake.

It also allows bad practice such as up front design, testing at the end by not encouraging a focus on the most important aspects of the delivery.

Short version. Prioritised does not contain an element of "only ordering by value" that was the original reason for the change. Ordered is weaker than prioritised, and can lead to malformed Scrum and/or bad PO practice. This is a small gap that inappropriate coaches and techniques such as SAFe can use to create poor scrum implementations.

In the PSM and PSPO there are great flow diagrams for the Sprint Planning, where Definition of Done and Retrospective Commitments are part of the input for the Sprint Planning. This is inconsistent with the way it is now described in the Scrum Guide.

From Scrum Guide, section Sprint Planning, subsection Topic One: What can be done this Sprint?
"The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team."

Suggestion: remove "the latest product Increment" (btw: in the rest of the guide it is called Increment), and replace it by Definition of Done and Retrospective Commitments.

Reason: Increment is input to the Sprint Review, and feedback is already translated to an update Product Backlog there. Definition of Done and Retrospective commitments are not mentioned anywhere in the Sprint Planning section, even though we do teach this.