Suggestions from review

Co-authored-by: Björn Gustavsson <bgustavsson@gmail.com>

Author: Maria-12648430

system/doc/reference_manual/data_types.md

@@ -402,7 +402,7 @@ adam
 {july,29}
 4> M2 = maps:update(age, 25, M1).
 #{age => 25,date => {july,29},name => adam}
-5> map_size(M1).
+5> map_size(M2).
 3
 6> map_size(#{}).
 0

system/doc/reference_manual/distributed.md

@@ -257,7 +257,7 @@ Here are some BIFs that are useful for distributed programming:
   can connect to other nodes, `false` otherwise.
 
 - [`monitor_node(Node, Bool)`](`erlang:monitor_node/2`) - Monitors the
-  status of `Node`. A message `{nodedown, Node}` is received if the
+  status of `Node`. A `{nodedown, Node}` message is received if the
   connection to it is lost.
 
 - `node/0` - Returns the name of the current node. Allowed in guards.

system/doc/reference_manual/expressions.md

@@ -755,7 +755,7 @@ there is no matching message in the message queue.
 > *not* necessarily the case. If the patterns in the clauses of the `receive`
 > expression only match specific messages and no such messages exist in the
 > message queue, the whole message queue needs to be inspected before the
-> timeout can occur. That is, the same as in
+> timeout can occur. That is, the same caveat as in
 > [the warning above](#selective-receive-warning) applies.
 
 The atom `infinity` will make the process wait indefinitely for a matching