diff --git a/README.md b/README.md
index 7d8a05dc49c..c05ddf388e3 100644
--- a/README.md
+++ b/README.md
@@ -1,33 +1,66 @@
 [![Build Status](https://travis-ci.org/cffi/cffi.svg?branch=master)](https://travis-ci.org/cffi/cffi)
 
-CFFI, the Common Foreign Function Interface, purports to be a portable
-foreign function interface for Common Lisp. The CFFI library is
-composed of a Lisp-implementation-specific backend in the CFFI-SYS
-package, and a portable frontend in the CFFI package.
+# What
+
+CFFI, the Common Foreign Function Interface, purports
+to be a portable FFI for Common Lisp. It abstracts away the
+differences between the API of the native FFI's of the various Common
+Lisp implementations.
+
+# How
+
+The CFFI library is composed of a Lisp-implementation-specific backend
+in the CFFI-SYS package, and a portable frontend in the CFFI package.
 
 The CFFI-SYS backend package defines a low-level interface to the
 native FFI support in the Lisp implementation. It offers operators for
 allocating and dereferencing foreign memory, calling foreign
 functions, and loading shared libraries.
 
-The CFFI frontend provides a declarative interface for defining
-foreign functions, structures, typedefs, enumerated types, etc. It is
-implemented in portable ANSI CL making use of the low-level operators
-exported by CFFI-SYS.
+The CFFI frontend provides a more comfortable, declarative interface
+for defining foreign functions, structures, typedefs, enumerated
+types, etc. It is implemented in portable ANSI CL making use of the
+low-level operators exported by CFFI-SYS.
+
+The CFFI-LIBFFI subsystem loads support for passing structs by
+value. It requires [libffi](https://sourceware.org/libffi/) for that.
+
+Please consult [the
+manual](http://common-lisp.net/project/cffi/manual/html_node/) for
+further details, including installation instructions.
+
+# Where
+
+Please visit [Github](https://github.com/cffi/cffi/issues) for bug
+reports, feature suggestions, the latest version, and to send your
+contributions. CFFI also has a [mailing
+list](https://mailman.common-lisp.net/listinfo/cffi-devel), and a
+project page at [cffi.common-lisp.dev](https://cffi.common-lisp.dev/).
+
+# Notes
+
+### CFFI/C2FFI
 
 CFFI/C2FFI is an ASDF-integrated mechanism to automatically generate a
-complete CFFI binding for a C project using the JSON output of
-[c2ffi](https://github.com/rpav/c2ffi). c2ffi generates its output by
-using LLVM/Clang as a library to parse any C project. Until CFFI/C2FFI
-is properly documented, please see these projects as examples:
+complete CFFI binding from a C header file. It requires a CLI tool
+called [c2ffi](https://github.com/rpav/c2ffi), but only for the
+developers of the libraries, not their users. `c2ffi` is written in
+C++, and it uses LLVM/Clang as the parsing library. It generates JSON
+output that can be checked in into the repositories. CFFI/C2FFI uses
+these JSON files to automatically generate a CL file that contains the
+CFFI definition forms. The generated bindings mirror the C namespace
+into an otherwise empty CL package as closely as possible. It means
+that they retain the upper/lower case of the names, and it also
+includes the `#define` macros as CL constants.
+
+Until CFFI/C2FFI is properly documented, you may check out these
+projects as examples:
 [hu.dwim.bluez](https://github.com/hu-dwim/hu.dwim.bluez),
 [hu.dwim.zlib](https://github.com/hu-dwim/hu.dwim.zlib),
 [hu.dwim.sdl](https://github.com/hu-dwim/hu.dwim.sdl), and
 [hu.dwim.mosquitto](https://github.com/attila-lendvai/hu.dwim.mosquitto).
 
-Please consult [the
-manual](http://common-lisp.net/project/cffi/manual/html_node/) for
-further details, including installation instructions.
+### Related projects
 
-Please visit [Github](https://github.com/cffi/cffi/issues) for bug
-reports and feature suggestions.
+- [cl-autowrap](https://github.com/rpav/cl-autowrap) is another
+  project that uses `c2ffi` to generate CFFI bindings.