Fix typos in Getting Started

Co-authored-by: Maria Scott <maria-12648430@hnc-agency.org>

Author: juhlig

system/doc/getting_started/conc_prog.md

@@ -71,7 +71,7 @@ done
 ```
 
 As shown, the function `say_something` writes its first argument the number of
-times specified by second argument. The function `start` starts two Erlang
+times specified by the second argument. The function `start` starts two Erlang
 processes, one that writes "hello" three times and one that writes "goodbye"
 three times. Both processes use the function `say_something`. Notice that a
 function used in this way by `spawn`, to start a process, must be exported from
@@ -149,7 +149,7 @@ start() ->
 ```erlang
 1> c(tut15).
 {ok,tut15}
-2> tut15: start().
+2> tut15:start().
 <0.36.0>
 Pong received ping
 Ping received pong
@@ -205,7 +205,7 @@ receive
    pattern2 ->
        actions2;
    ....
-   patternN
+   patternN ->
        actionsN
 end.
 ```
@@ -254,7 +254,7 @@ process "ping":
 Ping_PID ! pong
 ```
 
-Notice how the operator "\!" is used to send messages. The syntax of "\!" is:
+Notice how the operator `!` is used to send messages. The syntax of `!` is:
 
 ```erlang
 Pid ! Message
@@ -283,7 +283,7 @@ Pong_PID ! {ping, self()},
 ```
 
 `self/0` returns the pid of the process that executes `self/0`, in this case the
-pid of "ping". (Recall the code for "pong", this lands up in the variable
+pid of "ping". (Recall the code for "pong", this ends up in the variable
 `Ping_PID` in the `receive` previously explained.)
 
 "Ping" now waits for a reply from "pong":
@@ -397,7 +397,7 @@ pong ! {ping, self()},
 ## Distributed Programming
 
 Let us rewrite the ping pong program with "ping" and "pong" on different
-computers. First a few things are needed to set up to get this to work. The
+computers. First a few things need to be set up to get this to work. The
 distributed Erlang implementation provides a very basic authentication mechanism
 to prevent unintentional access to an Erlang system on another computer. Erlang
 systems which talk to each other must have the same _magic cookie_. The easiest
@@ -438,7 +438,7 @@ Erlang system running on a computer is called an _Erlang node_.
 
 (Note: `erl -sname` assumes that all nodes are in the same IP domain and we can
 use only the first component of the IP address, if we want to use nodes in
-different domains we use `-name` instead, but then all IP address must be given
+different domains we use `-name` instead, but then all IP addresses must be given
 in full.)
 
 Here is the ping pong example modified to run on two separate nodes:
@@ -533,7 +533,7 @@ Pong finished
 
 Looking at the `tut17` code, you see that the `pong` function itself is
 unchanged, the following lines work in the same way irrespective of on which
-node the "ping" process is executes:
+node the "ping" process is executed:
 
 ```erlang
 {ping, Ping_PID} ->
@@ -623,7 +623,7 @@ Before starting, notice the following:
 - This example only shows the message passing logic - no attempt has been made
   to provide a nice graphical user interface, although this can also be done in
   Erlang.
-- This sort of problem can be solved easier by use of the facilities in OTP,
+- This sort of problem can be solved more easily by using the facilities in OTP,
   which also provide methods for updating code on the fly and so on (see
   [OTP Design Principles](`e:system:design_principles.md`)).
 - The first program contains some inadequacies regarding handling of nodes which
@@ -666,9 +666,6 @@ File `messenger.erl`:
 %%% Reply {messenger, logged_on} logon was successful
 %%%
 %%% To server: {ClientPid, logoff}
-%%% Reply: {messenger, logged_off}
-%%%
-%%% To server: {ClientPid, logoff}
 %%% Reply: no reply
 %%%
 %%% To server: {ClientPid, message_to, ToName, Message} send a message
@@ -697,7 +694,7 @@ server_node() ->
     messenger@super.
 
 %%% This is the server process for the "messenger"
-%%% the user list has the format [{ClientPid1, Name1},{ClientPid22, Name2},...]
+%%% the user list has the format [{ClientPid1, Name1},{ClientPid2, Name2},...]
 server(User_List) ->
     receive
         {From, logon, Name} ->
@@ -734,7 +731,7 @@ server_logoff(From, User_List) ->
     lists:keydelete(From, 1, User_List).
 
 
-%%% Server transfers a message between user
+%%% Server transfers a message between users
 server_transfer(From, To, Message, User_List) ->
     %% check that the user is logged on and who he is
     case lists:keysearch(From, 1, User_List) of
@@ -894,7 +891,7 @@ call. This would result in the process getting bigger and bigger for every loop.
 
 Functions in the `lists` module are used. This is a very useful module and a
 study of the manual page is recommended (`erl -man lists`).
-`lists:keymember(Key,Position,Lists)` looks through a list of tuples and looks
+`lists:keymember(Key,Position,List)` looks through a list of tuples and looks
 at `Position` in each tuple to see if it is the same as `Key`. The first element
 is position 1. If it finds a tuple where the element at `Position` is the same
 as `Key`, it returns `true`, otherwise `false`.
@@ -986,7 +983,7 @@ From ! {messenger, stop, you_are_not_logged_on}
 
 This is received by the client, which in turn does [`exit(normal)`](`exit/1`)
 and terminates. If `keysearch` returns `{value,{From,Name}}` it is certain that
-the user is logged on and that his name (peter) is in variable `Name`.
+the user is logged on and that their name (peter) is in the variable `Name`.
 
 Let us now call:
 

system/doc/getting_started/records_macros.md

@@ -59,7 +59,7 @@ introduced:
 %%% Configure the location of the server node,
 -define(server_node, messenger@super).
 
-%%%----END FILE----
+%%%----END FILE-----
 ```
 
 ```erlang
@@ -89,7 +89,7 @@ introduced:
 -record(message_to,{to_name, message}).
 %%% logoff
 
-%%%----END FILE----
+%%%----END FILE-----
 ```
 
 ```erlang
@@ -135,7 +135,7 @@ message(ToName, Message) ->
              ok
 end.
 
-%%%----END FILE----
+%%%----END FILE-----
 ```
 
 ```erlang
@@ -178,7 +178,7 @@ await_result() ->
             exit(timeout)
     end.
 
-%%%----END FILE---
+%%%----END FILE----
 ```
 
 ```erlang
@@ -194,7 +194,7 @@ server() ->
     process_flag(trap_exit, true),
     server([]).
 
-%%% the user list has the format [{ClientPid1, Name1},{ClientPid22, Name2},...]
+%%% the user list has the format [{ClientPid1, Name1},{ClientPid2, Name2},...]
 server(User_List) ->
     io:format("User list = ~p~n", [User_List]),
     receive
@@ -230,7 +230,7 @@ server_logon(From, Name, User_List) ->
 server_logoff(From, User_List) ->
     lists:keydelete(From, 1, User_List).
 
-%%% Server transfers a message between user
+%%% Server transfers a message between users
 server_transfer(From, To, Message, User_List) ->
     %% check that the user is logged on and who he is
     case lists:keysearch(From, 1, User_List) of
@@ -250,7 +250,7 @@ server_transfer(From, Name, To, Message, User_List) ->
             From !  #server_reply{message=sent}
     end.
 
-%%%----END FILE---
+%%%----END FILE----
 ```
 
 ## Header Files
@@ -269,7 +269,7 @@ for example:
 ```
 
 In the case above the file is fetched from the same directory as all the other
-files in the messenger example. (_manual_).
+files in the messenger example. (_manual_)
 
 .hrl files can contain any valid Erlang code but are most often used for record
 and macro definitions.
@@ -297,7 +297,7 @@ This is equivalent to:
 Creating a record is best illustrated by an example:
 
 ```erlang
-#message_to{message="hello", to_name=fred)
+#message_to{message="hello", to_name=fred}
 ```
 
 This creates:
@@ -306,8 +306,8 @@ This creates:
 {message_to, fred, "hello"}
 ```
 
-Notice that you do not have to worry about the order you assign values to the
-various parts of the records when you create it. The advantage of using records
+Notice that you do not have to worry about the order in which you assign values to the
+various parts of a record when you create it. The advantage of using records
 is that by placing their definitions in header files you can conveniently define
 interfaces that are easy to change. For example, if you want to add a new field
 to the record, you only have to change the code where the new field is used and
@@ -358,7 +358,7 @@ This is a standard macro (that is, defined by the system, not by the user).
 of using macros with, for example, [parameters](macros.md#defining-and-using-macros).
 
 The three Erlang (`.erl`) files in the messenger example are individually
-compiled into object code file (`.beam`). The Erlang system loads and links
+compiled into object code files (`.beam`). The Erlang system loads and links
 these files into the system when they are referred to during execution of the
 code. In this case, they are simply put in our current working directory (that
 is, the place you have done "cd" to). There are ways of putting the `.beam`

system/doc/getting_started/robustness.md

@@ -25,7 +25,7 @@ Several things are wrong with the messenger example in
 [A Larger Example](conc_prog.md#ex). For example, if a node where a user is
 logged on goes down without doing a logoff, the user remains in the server's
 `User_List`, but the client disappears. This makes it impossible for the user to
-log on again as the server thinks the user already is logged on.
+log on again as the server thinks the user is already logged on.
 
 Or what happens if the server goes down in the middle of sending a message,
 leaving the sending client hanging forever in the `await_result` function?
@@ -115,7 +115,7 @@ is canceled if `{ping,Ping_PID}` is received. If `{ping,Ping_PID}` is not
 received, the actions following the time-out are done after 5000 milliseconds.
 `after` must be last in the `receive`, that is, preceded by all other message
 reception specifications in the `receive`. It is also possible to call a
-function that returned an integer for the time-out:
+function that returns an integer for the time-out:
 
 ```erlang
 after pong_timeout() ->
@@ -221,7 +221,7 @@ sent to "pong", which also terminates.
 
 It is possible to modify the default behaviour of a process so that it does not
 get killed when it receives abnormal exit signals. Instead, all signals are
-turned into normal messages on the format `{'EXIT',FromPID,Reason}` and added to
+turned into normal messages of the format `{'EXIT',FromPID,Reason}` and added to
 the end of the receiving process' message queue. This behaviour is set by:
 
 ```erlang
@@ -346,7 +346,7 @@ server_node() ->
     messenger@super.
 
 %%% This is the server process for the "messenger"
-%%% the user list has the format [{ClientPid1, Name1},{ClientPid22, Name2},...]
+%%% the user list has the format [{ClientPid1, Name1},{ClientPid2, Name2},...]
 server() ->
     process_flag(trap_exit, true),
     server([]).
@@ -387,7 +387,7 @@ server_logoff(From, User_List) ->
     lists:keydelete(From, 1, User_List).
 
 
-%%% Server transfers a message between user
+%%% Server transfers a message between users
 server_transfer(From, To, Message, User_List) ->
     %% check that the user is logged on and who he is
     case lists:keysearch(From, 1, User_List) of
@@ -469,10 +469,10 @@ unreachable for one of the following reasons:
 - The user has logged off (the "logoff" message is removed).
 - The network connection to the client is broken.
 - The node on which the client process resides has gone down.
-- The client processes has done some illegal operation.
+- The client process has done some illegal operation.
 
 If an exit signal is received as above, the tuple `{From,Name}` is deleted from
-the servers `User_List` using the `server_logoff` function. If the node on which
+the server's `User_List` using the `server_logoff` function. If the node on which
 the server runs goes down, an exit signal (automatically generated by the
 system) is sent to all of the client processes:
 `{'EXIT',MessengerPID,noconnection}` causing all the client processes to