diff options
| author | Ryan Mast <nightlark@users.noreply.github.com> | 2017-07-09 08:51:23 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-09 08:51:23 +0300 |
| commit | 1859f6a5f59115702c1db6000a775286340e680d (patch) | |
| tree | a25c3fb82031e9fcc5856b4ee9310c1d887676c7 | |
| parent | 47697e1414dd2aaf59d4df61edb70f36058069f1 (diff) | |
Added missing 'S' in NanoSVG
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -17,7 +17,7 @@ That is, you should get the same looking data as your designed in your favorite NanoSVG can return the paths in few different units. For example if you want to render an image, you may choose to get the paths in pixels, or if you are feeding the data into a CNC-cutter, you may want to use millimeters. -The units passed to NanoVG should be one of: 'px', 'pt', 'pc' 'mm', 'cm', or 'in'. +The units passed to NanoSVG should be one of: 'px', 'pt', 'pc' 'mm', 'cm', or 'in'. DPI (dots-per-inch) controls how the unit conversion is done. If you don't know or care about the units stuff, "px" and 96 should get you going. @@ -97,4 +97,4 @@ $ ./example # License -The library is licensed under [zlib license](LICENSE.txt)
\ No newline at end of file +The library is licensed under [zlib license](LICENSE.txt) |