Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/memononen/nanosvg.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMikko Mononen <memononen@gmail.com>2017-07-09 11:46:20 +0300
committerGitHub <noreply@github.com>2017-07-09 11:46:20 +0300
commit9a74da4db5ac74083e444010d75114658581b9c7 (patch)
treea25c3fb82031e9fcc5856b4ee9310c1d887676c7
parent47697e1414dd2aaf59d4df61edb70f36058069f1 (diff)
parent1859f6a5f59115702c1db6000a775286340e680d (diff)
Merge pull request #99 from nightlark/patch-1
Added missing 'S' in NanoSVG
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index a672d6f..05af334 100644
--- a/README.md
+++ b/README.md
@@ -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)