diff --git a/docs/lib.md b/docs/lib.md
index 5e7841cf..960b98fd 100644
--- a/docs/lib.md
+++ b/docs/lib.md
@@ -1,11 +1,73 @@
 # Build wolfBoot as Library
 
-## Example Build steps
+Instead of building as standalone repository, wolfBoot can be built as
+a secure-boot library and integrated in third party bootloaders, custom
+staging solutions etc.
+
+
+## Library API
+
+The wolfBoot secure-boot image verification has a very simple interface.
+The core object describing the image is a `struct wolfBoot_image`, which
+is initialized when `wolfBoot_open_image_address()` is called. The signature is:
+
+
+`int wolfBoot_open_image_address(struct wolfBoot_image* img, uint8_t* image)`
+
+
+where `img` is a pointer to a local (uninitialized) structure of type `wolfBoot_image`, and
+`image` is a pointer to where the signed image is mapped in memory, starting from the beginning
+of the manifest header.
+
+
+On success, zero is returned. If the image does not contain a valid 'magic number' at the beginning
+of the manifest, or if the size of the image is bigger than `WOLFBOOT_PARTITION_SIZE`, -1 is returned. 
+
+
+If the `open_image_address` operation is successful, two other functions can be invoked:
+
+
+- `int wolfBoot_verify_integrity(struct wolfBoot_image *img)`
+
+
+This function verifies the integrity of the image, by calculating the SHA hash of the image content,
+and comparing it with the digest stored in the manifest header. `img` is a pointer to
+an object of type `wolfBoot_image`, previously initialized by `wolfBoot_open_image_address`.
+
+
+0 is returned if the image integrity could be successfully verified, -1 otherwise.
+
+
+
+- `int wolfBoot_verify_authenticity(struct wolfBoot_image *img)`
+
+
+This function verifies that the image content has been signed by a trusted
+counterpart (i.e. that could be verified using one of the public keys available).
+
+
+`0` is returned in case of successful authentication,  `-1` if anything went wrong during the operation,
+and `-2` if the signature could be found, but was not possible to authenticate against its public key.
+
+## Library mode: example application
+
+An example application is provided in `hal/library.c`.
+
+The application `test-lib` opens a file from a path passed as argument
+from the command line, and verifies that the file contains a valid, signed
+image that can be verified for integrity and authenticity using wolfBoot in library
+mode.
+
+## Configuring and compiling the test-lib application
+
+Step 1: use the provided configuration to compile wolfBoot in library mode:
 
 ```
-ln -s config/examples/library.config .config
+cp config/examples/library.config .config
 ```
 
+Step 2: create a file `target.h` that only contains the following lines:
+
 ```
 cat > include/target.h << EOF
 #ifndef H_TARGETS_TARGET_
@@ -21,17 +83,43 @@ cat > include/target.h << EOF
 EOF
 ```
 
+Change `WOLFBOOT_PARTITION_SIZE` accordingly. `wolfBoot_open_image_address()` will discard images larger than
+`WOLFBOOT_PARTITION_SIZE` - `IMAGE_HEADER_SIZE`.
+
+
+Step 3: compile keytools and create keys.
+
 ```
-touch empty
 make keytools
 ./tools/keytools/keygen --ed25519 src/ed25519_pub_key.c
+```
+
+
+Step 4: Create an empty file and sign it using the private key.
+
+```
+touch empty
 ./tools/keytools/sign --ed25519 --sha256 empty ed25519.der 1
 ```
 
+
+Step 5: compile the test-lib application, linked with wolfBoot in library mode, and the
+public key from the keypair created at step 4.
+
 ```
 make test-lib
-./test-lib empty_v1_signed.bin
+```
 
+Step 6: run the application with the signed image
+
+```
+./test-lib empty_v1_signed.bin
+```
+
+If everything went right, the output should be similar to:
+
+```
 Firmware Valid
 booting 0x5609e3526590(actually exiting)
 ```
+