Aggregate in domain event example

As stated in the beginning of the page: `use domain events to explicitly implement side effects across multiple aggregates` and also the purpose of domain events is to notify that something has already happened.
I believe that use domain entity Order in 'Implement domain events' section isn't appropriate because in this case one can call methods on the entity and produce even more side effects for this aggregate.
Of course as usual 'it depends' but I think it worth to mention consequences of such approach.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: d432d5bb-24a7-3bec-1e17-910c8129226e
* Version Independent ID: e41af96d-f015-a8e0-4449-7a508d7bccc8
* Content: [Domain events. design and implementation](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/domain-events-design-implementation)
* Content Source: [docs/architecture/microservices/microservice-ddd-cqrs-patterns/domain-events-design-implementation.md](https://github.com/dotnet/docs/blob/master/docs/architecture/microservices/microservice-ddd-cqrs-patterns/domain-events-design-implementation.md)
* Product: **dotnet-architecture**
* Technology: **microservices**
* GitHub Login: @nishanil
* Microsoft Alias: **nanil**