Grammer and typo fixes in readme

Readme.md

@@ -4,24 +4,24 @@ This is a port of the [VEFontCache](https://github.com/hypernewbie/VEFontCache)
 
 Its original purpose was for use in game engines, however its rendeirng quality and performance is more than adequate for many other applications.
 
-See: [docs/Readme.md](docs/Readme.md) for the library's interface
+See: [docs/Readme.md](docs/Readme.md) for the library's interface.
 
 ## Building
 
 See [scripts/Readme.md](scripts/Readme.md) for building examples or utilizing the provided backends.
 
-Currently the scripts provided & the library itself where developed & tested on Windows. The library itself should not be limited to that OS platform however, just don't have the configuration setup for alternative platforms (yet).
+Currently the scripts provided & the library itself were developed & tested on Windows. The library however should not be limited to that OS platform, just don't have the configuration for alternative platforms (yet).
 
-The library depends on freetype, harfbuzz, & stb_truetype currently to build.  
+The library depends on freetype, harfbuzz, & stb_truetype to build.  
 Note: freetype and harfbuzz could technically be gutted if the user removes their definitions, however they have not been made into a conditional compilation option (yet).
 
 ## Changes from orignal
 
-* Font Parser & Glyph shaper are abstracted to their own interface
+* Font Parser & Glyph shaper are abstracted to their own warpper interface
 * ve_fontcache_loadfile not ported (ust use core:os or os2, then call load_font)
 * Macro defines have been coverted (mostly) to runtime parameters
 * Support for hot_reloading
-* Curve quality step granularity for glyph rendering can be set on a per font basis.
+* Curve quality step intropolation for glyph rendering can be set on a per font basis.
 
 ## TODOs
 
@@ -35,18 +35,12 @@ Note: freetype and harfbuzz could technically be gutted if the user removes thei
 
 ### Optimization:
 
-* Check if its better to store the generated glyph vertices if they need to be re-cached or directly drawn.
+* Check if its better to store the glyph vertices if they need to be re-cached to atlas or directly drawn.
 * Look into setting up multi-threading by giving each thread a context
   * There is a heavy performance bottleneck in iterating the text/shape/glyphs on the cpu (single-thread) vs the actual rendering *(if doing thousands of drawing commands)*
   * draw_text can provide in the context a job list per thread for the user to thenk hookup to their own threading solution to handle.
   * Context would need to be segregated into staged data structures for each thread to utilize
-    * Each should have their own?
-      * draw_list
-      * draw_layer
-      * atlas.next_idx
-      * glyph_draw_buffer
-      * shape_cache
-    * This would need to converge to the singlar draw_list on a per layer basis (then user reqeusts a draw_list layer there could a yield to wait for the jobs to finish); if the interface expects the user to issue the commands single-threaded unless, we just assume the user is going to feed the gpu the commands & data through separate threads as well (not ideal ux).
+    * This would need to converge to the singlar draw_list on a per layer basis. The interface expects the user to issue commands single-threaded unless, its assumed the user is going to feed the gpu the commands & data through separate threads as well (not ideal ux).
   * How the contexts are given jobs should be left up to the user (can recommend a screen quadrant based approach in demo examples)
 
 Failed Attempts:

docs/Readme.md

@@ -3,7 +3,9 @@
 Notes
 ---
 
-Freetype implementation supports specifying a FT_Memory handle which is a pointer to a FT_MemoryRect. This can be used to define an allocator for the parser. Currently this library does not wrap this interface (yet). If using freetype its recommend to update `parser_init` with the necessary changes to wrap the context's backing allocator for freetype to utilize.
+The freetype setup is not finished. Specifically due to cache_glyph_freetype not parsing the glyph outline data structure properly. 
+
+Freetype supports specifying a FT_Memory handle which is a pointer to a FT_MemoryRect. This can be used to define an allocator for the parser. Currently this library does not wrap this interface (yet). If using freetype its recommend to update `parser_init` with the necessary changes to wrap the context's backing allocator for freetype to utilize.
 
 ```c
   struct  FT_MemoryRec_
@@ -15,19 +17,19 @@ Freetype implementation supports specifying a FT_Memory handle which is a pointe
   };
   ```
 
-This library (seems) to perform best if the text commands are fed in 'whitespace aware chunks', where instead of feeding it entire blobs of text, the user identfies the "words" in the text and feeding the visible and whitespce chunks derived from this to draw_text as separate calls. This improves the caching of the text shapes. The downside is there has to be a time where the text is parsed into tokens beforehand so that the this iteration does not have to occur continously.
+This library (seems) to perform best if the text commands are fed in 'whitespace aware chunks', where instead of feeding it entire blobs of text, the user identfies "words" in the text and feeding the visible and whitespce chunks derived from this to draw_text as separate calls. It improves the caching of the text shapes. The downside is there has to be a time where the text is parsed into tokens beforehand so that the this iteration does not have to occur continously.
 
 ### startup
 
 Initializes a provided context.
 
-There are a large amount of parameters to tune the library instance to the user's preference. By default, keep in mind the library defaults to utilize stb_truetype as the font parser and harfbuzz (soon...) for the shaper.
+There are a large amount of parameters to tune the library instance to the user's preference. By default, keep in mind the library defaults to utilize stb_truetype as the font parser and harfbuzz for the shaper.
 
-Much of the data structures within the context struct are not fixed-capacity allocations so make sure that the backing allocator utilized can handle it.
+Much of the data structures within the context struct are not fixed-capacity allocations so make sure that the backing allocator can handle it.
 
 ### hot_reload
 
-The library supports being used in a dynamically loaded module. If this occurs simply make sure to call this procedure with a reference to the backing allocator provided during startup as all dynamic containers tend to lose a proper reference to the allocator's procedure.
+The library supports being used in a dynamically loaded module. If its hot-reloaded simply make sure to call this procedure with a reference to the backing allocator provided during startup as all dynamic containers tend to lose a proper reference to the allocator's procedure.
 
 ### shutdown
 
@@ -45,7 +47,7 @@ Will provide the current cursor_pos for the resulting text drawn.
 
 ### set_color
 
-Sets the color to utilize on `DrawCall`s for FrameBuffer.Target or .Target_Uncached passes
+Sets the color to utilize on `Draw_Call`s for FrameBuffer.Target or .Target_Uncached passes
 
 ### get_draw_list
 
@@ -55,8 +57,8 @@ By default, if get_draw_list is called, it will first call `optimize_draw_list`
 ###  get_draw_list_layer
 
 Get the enqueued draw_list for the current "layer".
-A layer is considered the slice of the drawlist's content from the last call to `flush_draw_list_layer` onward.
-By default, if get_draw_list_layer is called, it will first call `optimize_draw_list` for the user to optimize the slice (exlusively) of the draw list's draw calls. If this is undesired, make sure to pass `optimize_before_returning = false` in the arguments.
+A layer is considered the slice of the `Draw_List`'s content from the last call to `flush_draw_list_layer` onward.
+By default, if `get_draw_list_layer` is called, it will first call `optimize_draw_list` for the user to optimize the slice (exlusively) of the draw list's draw calls. If this is undesired, make sure to pass `optimize_before_returning = false` in the arguments.
 
 The draw layer offsets are cleared with `flush_draw_list`
 
@@ -70,7 +72,7 @@ Will update the draw list layer with the latest offset based on the current leng
 
 ### measure_text_size
 
-Provides a Vec2 the width and height occupied by the provided text string. The y is measured to be the the largest glyph box bounds height of the text. The width is derived from the `end_cursor_pos` field from a `ShapedText` entry.
+Provides a Vec2 the width and height occupied by the provided text string. The y is measured to be the the largest glyph box bounds height of the text. The width is derived from the `end_cursor_pos` field from a `Shaped_Text` entry.
 
 ### get_font_vertical_metrics