Wording

README.md

@@ -26,7 +26,7 @@ User Interface Proof of Concept and Demo: [logixUX](https://github.com/Phuire-Re
 
 *Note: This becomes necessary to set once your application grows in complexity. As the fundamental issue with graph programming, is that at a sufficient scale. You are fighting your computers branch prediction. You can think of the run time of Stratimux like a balloon. In theory as long as your logic is clean, you shouldn't run into race conditions. But the unfortunate truth is that the more logic that your balloon if filled with. The higher likelihood your balloon will pop. So to avoid this, you need to supply a beat to complex plans that might overinflate your balloon.*
 
-*This is counter intuitive to most programming, but is the trade off for this new dynamic paradigm. As computers have been designed for transactional object oriented programming. This paradigm moves beyond that comfortable scale of complexity and reveals the generally good enough design of the computers we rely upon. Funny to say that you can write by hand a program that hallucinates. **hint***
+*This is counter intuitive to most programming, but is the trade off for this new dynamic paradigm. As computers have been designed for transactional object oriented programming. This paradigm moves beyond that comfortable scale of complexity and reveals the generally good enough design of the computers we rely upon. Funny to say that you can write a program by hand that hallucinates. **hint***
 ### 11/26/23
 * Updated naming conventions throughout. Counter is now CounterState. Strategies now export with their associated concept's prepended.
 * Added parsing tokens. If curious about this functionality see the logixUX project. These tokens in combination with that project will upon its release. Allow for the ease of parsing Stratimux or other TypeScript projects into high quality training data.