diff --git a/doc/README.md b/doc/README.md
new file mode 100644
index 000000000..7a319c3d7
--- /dev/null
+++ b/doc/README.md
@@ -0,0 +1,9 @@
+# Building the documentation
+
+For CMake to configure building documentation,
+install Doxygen, as well Python 3.x with
+Sphinx and Breathe. For the latter, run::
+
+  pip install -r requirements.txt
+
+See https://mp.ampl.com/intro.html#building-the-documentation.
diff --git a/doc/source/components.rst b/doc/source/components.rst
index c3461f27f..d835b2d97 100644
--- a/doc/source/components.rst
+++ b/doc/source/components.rst
@@ -139,44 +139,58 @@ Writing NL and reading SOL files
 
 For modeling systems and applications using AMPL solvers,
 MP provides a library to write NL and read SOL files.
-The library is zero-overhead: it does not store the model,
+The library is virtually zero-overhead: it does not store the model,
 nor does it require any intermediate objects to represent
 model information.
 
 NL Writer design
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The library
-allows a most efficient conversion of a user model's
-internal representation to NL format by providing
-NL component writer callbacks
-(and solution reader callbacks to receive solutions.)
+The NL writer library provides two approaches:
 
-In turn, the library is flexible to use because
-various components of the user model will be provided
-on the library's request from a user-specialized
-`~mp::NLFeeder2` object (for solution input,
-solution components will be received by methods
-of a custom `~mp::SOLHandler2` class.)
+1. "Straightforward" API via `~mp::NLModel` and
+   `~mp::NLSolver`. This is currently limited to
+   (MI)LP and (MI)QP models.
+
+2. Full NL API via callbacks into custom
+   `~mp::NLFeeder2`
+   and `~mp::SOLHandler2` classes,
+   optionally via `~mp::NLSolver`.
+
+   This approach
+   allows a most efficient conversion of a user model's
+   internal representation to NL format by providing
+   NL component writer callbacks
+   (and solution reader callbacks to receive solutions.)
+
+   In turn, the library is flexible to use because
+   various components of the user model are provided
+   on the library's request from a user-specialized
+   `~mp::NLFeeder2`
+   object (for solution input,
+   solution components are received by methods
+   of a custom `~mp::SOLHandler2` class.)
 
 .. image:: images/NLWriter.svg
 
 
-NL Writer APIs
+NL Writer API languages
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- **NL Writer C++ API** is provided by classes
-  `~mp::NLSolver`, `~mp::NLFeeder2`, `~mp::SOLHandler2`.
-  See
-  `C++ API example </~https://github.com/ampl/mp/blob/develop/nl-writer2/examples/cpp/nlsol_ex.cc>`_
-  solving a small non-linear model.
-
-- **NL Writer C API** is provided by structs
-  `~NLW2_NLSolver_C`, `~NLW2_NLFeeder2_C`, `~NLW2_SOLHandler2_C`.
-  *Currently only linear models are supported.*
-  See
-  `C API example </~https://github.com/ampl/mp/blob/develop/nl-writer2/examples/c/nlsol_ex_c.c>`_
-  solving a small linear model.
+See the
+`NL Writer example folder </~https://github.com/ampl/mp/blob/develop/nl-writer2/examples/>`_
+and tests.
+
+- **C++ API** is provided by classes
+  `~mp::NLSolver`, `~mp::NLModel`, `~mp::NLFeeder2`, `~mp::SOLHandler2`.
+
+- **C API** is provided by structs
+  `~NLW2_NLSolver_C`, `~NLW2_NLModel_C`,
+  `~NLW2_NLFeeder2_C`, `~NLW2_SOLHandler2_C`.
+
+  - Currently only (MI)LP/(MI)QP (via `~NLW2_NLModel_C`)
+    or linear models (via `~NLW2_NLFeeder2_C`, `~NLW2_SOLHandler2_C`)
+    are supported.
 
 
 .. _recommended-driver-logic:
diff --git a/nl-writer2/include/api/c/nl-model-c.h b/nl-writer2/include/api/c/nl-model-c.h
index 5c5feb72d..861877753 100644
--- a/nl-writer2/include/api/c/nl-model-c.h
+++ b/nl-writer2/include/api/c/nl-model-c.h
@@ -1,5 +1,5 @@
 /**
- * C API: extern "C" wrapper for mp::NLSolver class
+ * C API: extern "C" wrapper for mp::NLModel class
  *
  */