this should now fix #2 some sentances have been reworded so the links to the code make more sense

README.md

@@ -1,17 +1,16 @@
 # c_state_pattern
 
-A simple example of how to implement the state pattern in c. check [`main.c`](src/main.c) for the implementation.
+A simple example of how to implement the state pattern in c. Check [`main.c`](src/main.c) for the implementation.
 
-the state pattern is a pattern that aims to get rid of the mess that a state machine causes within your code. So i propose a problem for you, you are trying to write an state machine for a phone, sounds easy your phone only has 3 inputs that change the current state of the phone.
+The state pattern is a pattern allows for greater flexibility, maintainability as well as reducing decoupling between states over using a state machine using conditional statements. So i propose a problem for you, you are trying to write an state machine for a phone, sounds easy your phone only has 3 inputs that change the current state of the phone.
 
+This 
 #### inputs:
 - power button
 - lock button
 - string enter button
 
-the power button does what it says either turns the phone off or on, the lock button too does what it says on the tin locks the phone, lastly the string enter button enters what every string is in the phones buffer this is used for entering things like passwords to unlock the phone.
+The power button does what it says either turns the phone off or on, the lock button too does what it says `on the tin locks the phone, lastly the string enter button enters what every string is in the phones buffer this is used for entering things like passwords to unlock the phone. Using these buttons you determine you need 4 states for your phone these are:
-
-using these buttons you determine you need 4 states for your phone these are:
 
 #### states:
 - off
@@ -19,8 +18,9 @@ using these buttons you determine you need 4 states for your phone these are:
 - locked
 - debug
 
-and you want the inter-action between these states to work as follows:
+And you want the inter-action between these states to work as follows:
 
+#### state diagram
 ```
 pwr : power button pressed
 lck : lock button pressed
@@ -40,8 +40,8 @@ str=x : string enter button press with string x
 │   │state   │            │state   │
 │   └──────┬─┘◄───┬───────┴──┬─────┘
 │     ▲    │     lck         │      
-│ lck ┤    ├ str=dbg         ├ str=dbg      
+│ lck ┤    │                 ├ str=dbg      
-│     │    │                 │      
+│     │    ├ str=dbg         │      
 │     │    │                 │      
 │     │    ▼                 │      
 │   ┌─┴──────┐               │      
@@ -52,48 +52,79 @@ str=x : string enter button press with string x
 ----------- \ state diagram -----------
 ```
 
-now you may read these requirements for the device and think ill just implement this with a state machine how bad can it be. Well your tech lead tells you that this systems needs to scaled to over 100 different states as they make the system more complex. you ask him "why do we need this" they reply back with management said so. And so between the idea of getting fired from throwing a brick at the management team and implementing this state diagram you decide you need this job and to implement state pattern.
+now you may read these requirements for the device and think ill just implement this with a state machine how bad can it be. Well your tech lead tells you that this systems needs to scaled to over 100 different states as they make the system more complex. You ask him "why do we need this" they reply back with management said so. And so between the idea of getting fired from throwing a brick at the management team and implementing this state diagram you decide you need this job and to implement state diagram. To start you beginning to implement this state diagram with a bog standard conditional state machine pattern as can be seen below. 
-this pattern allows for greater flexibility when creating new states, since you dont have to add to an ever gowning state machine. we do some simple math to see how out of hand this can get, 
+
-if we assume that you end up with 100 states in the end and each state takes up 20 odd line 
+```c
+
+void changeState(Device_t* device) {
+
+    State_e state = device->state;
+    
+    switch (state) {
+
+        case OFF:
+            if (offButtonPressed()) {
+                device->state = LOCK;
+            }
+            break;
+
+        case LOCK:
+            if (offButtonPressed()){
+                device->state = OFF:
+            }
+
+            if (strcmp(device->entered_string, "dbg") == 0) {
+                device->state = DEBUG:
+            }
+            
+            if (strcmp(device->entered_string, "pwd") == 0) {
+                device->state = UNLOCKED:
+            }
+            break;
+    ...
+```
+However like a good engineer you think back to what your tech lead said this system is going to have to scale to over 100 state. Currently you have implemented 2 states and the function is already over 20 lines of code (LOC) long. Assuming that as you add more states each state grows a little in lines of code and ends up somewhere with 20 LOC per state. We can do some simple math to see how out of hand this can get: 
 $$
-100_{\text{states}} \times 20_{\text{loc}} = 2000_{\text{loc}}
+100_{\text{states}} \times 20_{\text{LOC}} = 2000_{\text{LOC}}
 $$
-that would be a 2k line state machine and a nightmare to debug (i should know ive seen them in the wild)
+That would be a 2k LOC state machine and a nightmare to debug and maintain (i should know ive seen them in the wild, and let me tell you some LSP dont like it). 
+Therefor due to this mess of unmaintainable and heavily coupled code, you decide you need a different solution, and there for you decide to implement the namesake of this article **The state pattern**. Using this pattern all your states become singular easily maintainable [c files](/src/states/) as well as decoupling some states from the dependencies that other states need.
 
-so to start implement this pattern we first draw up a uml diagram of how it should go together. we can see we have the device itself and which is composed of a device state, and the entered string. 
+So to start implement this pattern we first draw up a uml diagram of how it should go together. We can see we have the device itself and which is composed of a device state, and the entered string. This "class" also has 3 methods pressPwrButton, pressStrInputButton, and pressLockButton. These methods are used to create an abstraction from the device state so the underlying state can change while using the same input functions. This means that the state field will change its self when one of the transition functions is called. These transition functions are the ones defined within the interface and the ones defined within the `Device_t` struct with the ones in the `Device_t` struct just calling the functions that are implemented by the `DeviceState_t`. To give and example when the devices `pressPwrButton` method is called this calls the `DeviceState_t` `pressPwrMethod`. 
 
+#### uml diagram
+```
+---------------------------------- UML Diagram ----------------------------------
 
-This "class" also has 3 methods pressPwrButton, pressStrInputButton, and pressLockButton. these methods are used to create an abstraction from the device state so the underlying state can change while using the same input functions.
+┌──────────────────────────────────────────────┐      ┌────────────────────────┐
+│ Device_t                                     │<>────┤ «interface»            │
+├──────────────────────────────────────────────┤      │ DeviceInterface_t      │
+│ +DeviceState_t state                         │      ├────────────────────────┤
+│ +String entered_string                       │      │                        │
+├──────────────────────────────────────────────┤      ├────────────────────────┤
+│ +pressPwrButton() : pressPwrMethod           │      │ +pressPwrMethod()      │
+│ +pressStrInputButton() : pressStrInputMethod │      │ +pressStrInputMethod() │
+│ +pressLockButton() : pressLockMethod         │      │ +pressLockMethod()     │
+└──────────────────────────────────────────────┘      └─────┬──────────────────┘
+             ▲                                              │                   
+             ▼                                              │                   
+             │                                              │                   
+             │                                              │                   
+┌────────────┴───────────────┐                              │                   
+│ DeviceState_t              │<>────────────────────────────┘                   
+├────────────────────────────┤                                               
+│ +String state_name         │                                               
+│ +DeviceInterface_s methods │                                               
+├────────────────────────────┤                                               
+│ +setDeviceStateToStateX()  │                                               
+└────────────────────────────┘                                               
 
-```mermaid
+--------------------------------- \ UML Diagram ---------------------------------
-classDiagram
-    class Device_t{
-        +DeviceState_t state
-        +String entered_string
-
-        +pressPwrButton() pressPwrMethod 
-        +pressStrInputButton() pressStrInputMethod
-        +pressLockButton() pressLockMethod
-    } 
-
-    class DeviceInterface_s {
-        +pressPwrMethod()
-        +pressStrInputMethod()
-        +pressLockMethod()
-    }
-
-    class DeviceState_t{
-        +String state_name
-        +DeviceInterface_s methods
-    }
-    Device_t *-- DeviceState_t
-    Device_t o-- DeviceInterface_s
-    DeviceInterface_s --o DeviceState_t
 
 ```
 (note not real uml diagram because no one knows how to read them)
 
-1. so to implement this we will first start off with the [device struct](/src/device.h#L64) 
+1. So to implement this we will first start off with the [device struct](/src/device.h#L64) 
     ```c
     // device.h
     typedef struct Device_s{
@@ -102,7 +133,7 @@ classDiagram
     } Device_t;
     ```
 
-2. Next we will implement the [methods](/src/device.h#L34) which in this case will be an [interface](https://en.wikipedia.org/wiki/Interface_(object-oriented_programming)). These methods are all the changes that can be made to the device i.e. your [inputs](#inputs).
+2. Next we will implement the [device interface](/src/device.h#L34) which as the name implies is an [interface](https://en.wikipedia.org/wiki/Interface_(object-oriented_programming)) bascially a struct that holds methods that creates a common set of functions that both structs need to implement. This means the [device interface](/src/device.h#L34) will defined 3 methods all relating to these transition functions which are all the changes that can be made to the device i.e. Your [inputs](#inputs).
 
     ```c
     // device.h
@@ -114,7 +145,7 @@ classDiagram
     ```
 
 
-3. and finally we will implement the [struct to hold the actual state](/src/device.h#L52) of the device. (note there is some funkiness in c with implementing this since you will need forward decls)
+3. And finally we will implement the [struct to hold the actual state](/src/device.h#L52) of the device. (note there is some funkiness in c with implementing this since you will need forward declaration)
     ```c
     // device.h
     typedef struct DeviceState_s{
@@ -122,14 +153,14 @@ classDiagram
         DeviceInterface_t methods;
     }DeviceState_t;
     ```
-4. now we need to implement the 3 functions for device inputs, ive implemented one here as the rest are very [similar](/src/device.c#L14). So this function takes the given device and then uses the methods defined within the device state to change the current state of the device. 
+4. Now we need to implement the 3 transition functions for device inputs, ive implemented one here as the rest are very [similar](/src/device.c#L14). So this function takes the given device and then uses the methods defined within the device state to change the current state of the device as defined within the [uml diagram](#uml-diagram). 
     ```c
     // device.c
     void pressPwrButton(Device_t *device) {
         device->state.methods.pressPwr(device);
     }
     ```
-5. now we will create a new header file called state, this file will contain the functions that sets the state of the given device to a new state. so we will implement a function per out defined [states](#states).
+5. Now we will create a new header file called state, this file will contain the functions that sets the state of the given device to a new state. So we will implement a function per out defined [states](#states).
     ```c
     //state.h
     void setDeviceStateToUnlock(Device_t *device);
@@ -137,7 +168,7 @@ classDiagram
     void setDeviceStateToLock(Device_t *device);
     void setDeviceStateToOff(Device_t *device);
     ```
-6. now we can implement one of these states as the rest of them should be fairly self explanatory. the state we will be implementing is the [lock state](/src/states/lock_state.c) as this should show off most of the different transitions. we will first start out with implementing the set state function. this function takes the given device and sets that devices state to this new state.
+6. Now we can implement one of these states as the rest of them should be fairly self explanatory. The state we will be implementing is the [lock state](/src/states/lock_state.c) as defined within the [state diagram](#state-diagram) since this should show off most of the different transitions. We will first start out with implementing the [set state function](/src/states/lock_state.c#L36). This function takes the given device and sets that devices state to this new state.
     ```c
     // lock_state.h
     void setDeviceStateToLock(Device_t *device) {
@@ -151,7 +182,7 @@ classDiagram
         };
     }
     ```
-7. now that we have the function for setting this state we can now implement the functions for what this functions does depending on the inputs we will first start with the power button function. This is one of the simplest when the power button is press i.e. when the function is called we set the devices state to off.
+7. Now that we have the function for setting this state we can now implement the functions defined within the [device interface](/src/device.h#L34). To start we will implement the simplest transition function, the [function](/src/states/lock_state.c#L10) called when the power button is press i.e. When the function is called we set the devices state to off.
     ```c
     // lock_state.c
     static void pressPwrMethod(Device_t *device) {
@@ -160,7 +191,7 @@ classDiagram
     }
 
     ```
-8. now we will implement the next function the lock button which in the lock state will do nothing.
+8. Now we will implement the next transition function, this time the [function](/src/states/lock_state.c#L31) is called when the lock button is pressed, which in the lock state will do nothing.
     ```c
     // lock_state.c
     static void pressLockMethod(Device_t *device) {
@@ -169,7 +200,7 @@ classDiagram
     }
     ```
     
-9. finally we create the function for handling the text input, this function will check the entered string to see if its either "dbg", or "pwd" and if it is enter debug or unlock respectively.
+9. Finally we create the transition function for handling the text input, this [function](/src/states/lock_state.c#L15) will check the entered string to see if its either "dbg", or "pwd" and if it is enter debug or unlock respectively.
     ```c
     static void pressStrInputMethod(Device_t *device) {
         if (strcmp(device->entered_string, "dbg") == 0) {
@@ -185,37 +216,40 @@ classDiagram
         printf("unknown string %s\n", device->entered_string);
     }
     ```
-10. now we just need to implement the other [states](#states) in the same way we implemented this first one.
+10. Now we just need to implement the other [states](#states) in the same way we implemented this first one.
-11. finally we need to test our device. firstly within main we create a new device and set its initial state to off.
+11. Finally we need to test our device. Firstly within [main](/src/main.c) we create a new device and set its initial state to off.
     ```c
+    // arrange:
     Device_t device;
     initDevice(&device);
     setDeviceStateToOff(&device);
     ```
-12. now we can test that the device correctly travels through each state, by pressing one of the buttons ([invoking the input method functions](/src/device.h#L34)) then checking that the `state_name` is equal to the set state name.
+12. Now we can test that the device correctly travels through each [state](#state-diagram), by pressing one of the buttons ([invoking the input method functions](/src/device.h#L34)) then checking that the `state_name` is equal to the set state name.
     ```c
-    
+    // act :
     // turn on the device
     pressPwrButton(&device);
-    if (strcmp(device.state.state_name, "lock_state.c") != 0) return 0;
 
+    // assert :
+    // check that the device entered the right state
+    if (strcmp(device.state.state_name, "lock_state.c") != 0) return 0;
     ```
 
-now that you have implement this basic state pattern your tech lead comes to you and tells you to implement one more state then they will let you throw a brick at management as a treat this state is:
+Now that you have implement this basic state pattern your tech lead comes to you and tells you to implement one more state then they will let you throw a brick at management as a treat this state is:
 - A calling state where:
     - when the phone is unlocked you can type in a number in the the string input and it will call it
     - you can also turn off the phone from this state
     - the lock button ends the current call and returns back to the unlocked state
 
-so try implementing this yourself.
+So try implementing this state yourself.
 
-other good resources for learning how this patterns works is [bob nystrom's game programming patterns book](https://gameprogrammingpatterns.com/state.html) as well as [refactoring Guru](https://refactoring.guru/design-patterns/state) however both of these implement this in the fun languages with object and interfaces.
+Other good resources for learning how this patterns works is [bob nystrom's game programming patterns book](https://gameprogrammingpatterns.com/state.html) as well as [refactoring Guru](https://refactoring.guru/design-patterns/state) however both of these implement this in the fun languages with object and interfaces.
 
 # how to build and run it
 
-this demo uses a simple build system called [nob](https://github.com/tsoding/nob.h) a header only build system for c projects.
+This demo uses a simple build system called [nob](https://github.com/tsoding/nob.h) a header only build system for c projects.
 
-to build run these command in the root of the project:
+To build run these command in the root of the project:
 ```bash
 
 # bootstraps the build system
@@ -228,4 +262,4 @@ to build run these command in the root of the project:
 > ./build/main 
 
 ```
-and if you have a different compiler you want to use that is posix compliant just change the `CC` macro in the `nob.c` with your one.
+And if you have a different compiler you want to use that is posix compliant just change the `CC` macro in the `nob.c` with your one.