Update CHANGES.md and NEWS.md for new release

[openssl.git] / NOTES-UNIX.md

diff --git a/NOTES-UNIX.md b/NOTES-UNIX.md
index 0b0a531db4a1cf681969a63a61761205def00206..fa52de68abc62ca176e2183e08ef0f97b1311fc9 100644 (file)
--- a/NOTES-UNIX.md
+++ b/NOTES-UNIX.md
@@ -49,6 +49,7 @@ Notes for UNIX-like platforms
  OpenSSL's configuration scripts recognise all these options and pass
  them to the Makefile that they build. (In fact, all arguments starting
  with `-Wl,` are recognised as linker options.)
+ Please note that 'l' in '-Wl' is lowercase L and not 1.
 
  Please do not use verbatim directories in your runtime shared library
  search path!  Some OpenSSL config targets add an extra directory level
@@ -100,14 +101,14 @@ Notes for UNIX-like platforms
  shared library face exactly the same problem with non-default locations.
  The OpenSSL config options mentioned above might or might not have bearing
  on linking of the target application. "Might" means that under some
- circumstances it would be sufficient to link with OpenSSL shared library
+ circumstances, it would be sufficient to link with OpenSSL shared library
  "naturally", i.e. with `-L/whatever/path -lssl -lcrypto`. But there are
  also cases when you'd have to explicitly specify runtime search path
  when linking your application. Consult your system documentation and use
  above section as inspiration...
 
  Shared OpenSSL builds also install static libraries. Linking with the
- latter is likely to require special care, because linkers usually look
+ latter is likely to require special care because linkers usually look
  for shared libraries first and tend to remain "blind" to static OpenSSL
  libraries. Referring to system documentation would suffice, if not for
  a corner case. On AIX static libraries (in shared build) are named