anchor.diff:  
   The Gremlin Console can be started in an "interactive" mode. Interactive mode is like <<execution-mode, execution mode>>
   but the console will not exit at the completion of the script, even if the script completes unsuccessfully. In such a
  -case, it will simply stop processing on the line that of the script that failed. In this way the state of the console
  -is such that a user could examine the state of things up to the point of failure which might make the script easier to
  +case, it will simply stop processing on the line of the script that failed. In this way, the state of the console
  +is such that a user could examine the state of things up to the point of failure, which might make the script easier to
   debug.
   
   In addition to debugging, interactive mode is a helpful way for users to initialize their console environment to
  
positive.code: Note that the user can now reference `g` (and `graph` for that matter) at startup without having to directly type that
  variable initialization code into the console.
  
  Like, execution mode, it is also possible to pass multiple scripts by specifying multiple `-i` options. See the
  <<execution-mode, Execution Mode Section>> for more information on the specifics of that capability.
  
  [[gremlin-console-docker-image]]
  
negative.code: 
  WARNING: Plugins must be compatible with the version of the Gremlin Console (or Gremlin Server) being used.  Attempts
  to use incompatible versions cannot be guaranteed to work.  Moreover, be prepared for dependency conflicts in
  third-party plugins that may only be resolved via manual jar removal from the `ext/{plugin}` directory.
  
  TIP: It is possible to manage plugin activation and deactivation by manually editing the `ext/plugins.txt` file which
  contains the class names of the "active" plugins.  It is also possible to clear dependencies added by `:install` by
  