Fixed typos

diff --git a/NEWS b/NEWS
index 2fecd4ac29622bbcafcaf0202739c2eaf622c0da..1a6aaa0787c146e2669bf512657343876d3fb2e6 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -36,7 +36,7 @@ API/ABI modifications: (see abi_compat_report in dev-utils/scripts)
     
 Misc:
 
-    * OpenJPEG is now officialy conformant with JPEG 2000 Part-1
+    * OpenJPEG is now officially conformant with JPEG 2000 Part-1
          and will soon become official reference software at the 
          JPEG committee.
        * Huge amount of bug fixes. See CHANGES for details.

diff --git a/README.md b/README.md
index 7161095495a52f420dad4c7443539a4f03485d33..ab31260c430add2e4814b8e8a8e826ca3ce280b1 100644 (file)
--- a/README.md
+++ b/README.md
@@ -36,11 +36,11 @@ See [NEWS](https://github.com/uclouvain/openjpeg/blob/master/NEWS) for user visi
 ## API/ABI
 
 OpenJPEG strives to provide a stable API/ABI for your applications. As such it
-only exposes a limited subset of its functions.  It uses a mecanism of
+only exposes a limited subset of its functions.  It uses a mechanism of
 exporting/hiding functions. If you are unsure which functions you can use in
 your applications, you should compile OpenJPEG using something similar to gcc:
 `fvisibility=hidden` compilation flag.
 See also: http://gcc.gnu.org/wiki/Visibility
 
-On windows, MSVC directly supports export/hidding function and as such the only
+On windows, MSVC directly supports export/hiding function and as such the only
 API available is the one supported by OpenJPEG.