diff --git a/docs/pages/aggregate.md b/docs/pages/aggregate.md
index cc4ae5ff9..adf0aa6f1 100644
--- a/docs/pages/aggregate.md
+++ b/docs/pages/aggregate.md
@@ -1,8 +1,8 @@
 # Aggregate
 
 The linchpin of event-sourcing is the aggregate. These aggregates can be imagined like entities in ORM. 
-One main difference is that we don't save the current state, but only the individual events that led to the state. 
-This means it is always possible to build the state again from the events.
+One main difference is that we don't save the current state, but only the individual events that led to the state.
+This means it is always possible to build the current state again from the events.
 
 !!! note
 
@@ -115,6 +115,7 @@ final class ProfileRegistered
 !!! note
 
     You can find out more about events [here](./events.md).
+    And for normalizer [here](./normalizer.md).
 
 After we have defined the event, we have to adapt the profile aggregate:
 
@@ -270,6 +271,10 @@ final class ChangeNameHandler
 }
 ```
 
+!!! success
+
+    Our aggregate can now be changed and saved.
+
 !!! note
 
     You can read more about Repository [here](./repository.md).