Diagram of structure of typical MojoLPM fuzzer.

This diagram may be helpful for contextual understanding of
the detailed steps elsewhere in this how-to.

Change-Id: Ib5fb340b214ba582d2fe5cbec32217e9e90291a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583206
Auto-Submit: Adrian Taylor <adetaylor@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#839010}

mojo/docs/mojolpm.md

@@ -382,6 +382,21 @@ concurrency loose ends, making sure that the fuzzer components are all running
 on the correct threads; those are more-or-less common to any fuzzer using
 MojoLPM.
 
+
+## Resulting structure
+
+Overall, the structure of your fuzzer is likely approximately to reflect that
+of the `content/test/fuzzer/presentation_service_mojolpm_fuzzer.cc`,
+shown here:
+
+![alt text](mojolpm-fuzzer-structure.png "Architecture diagram showing
+the rough structure of the presentation service fuzzer")
+
+(drawing source
+[here](https://goto.google.com/mojolpm-fuzzer-structure) )
+
+
+
 ## Test it!
 
 Make a corpus directory and fire up your shiny new fuzzer!