diff --git a/general/docs/changelogs/ch1_6_1.md b/general/docs/changelogs/ch1_6_1.md
index e629d5af916bfed0c50db03987947bbb0f893adb..e1ce796d3be38b372d2585384e2214fa933b4932 100644
--- a/general/docs/changelogs/ch1_6_1.md
+++ b/general/docs/changelogs/ch1_6_1.md
@@ -12,7 +12,7 @@ The high level changelog is available at http://research.microsoft.com/en-us/um/
  * Running TLC with both the `-generateSpecTE` flag will enable 'tool mode' output and, in the event that the model check encounters errors, generate a `SpecTE.tla` and `SpecTE.cfg` file pair that captures
  the state trace reconstruction in an Init-Next relation spec.
    * This `SpecTE.tla` will, by default, be a monolithic file, prefaced by the tool output, followed a the `SpecTE` MODULE definition which includes all extended non-StandardModule TLA code as well.
-     * To prevent the monolith inclusion of dependent TLA code, specify `-nomonolith`
+     * To prevent the monolith inclusion of dependent TLA code, specify `nomonolith` after the `-generateSpecTE`
  * Running TLC with `-h` now displays a usage page reminiscent of a standard man page.
  * TraceExplorer exposes four capabilities:
    * running the TraceExplorer with no spec name puts the TraceExplorer into a mode to receive input via stdin (e.g in order to pipe tool-mode output from TLC)