anchor.diff:  WildFly {wildflyVersion} but can easily be replaced with your own if desired.
   
   [[managing-your-wildfly-10]]
  -==== Managing your WildFly {wildflyVersion}
  +== Managing your WildFly {wildflyVersion}
   
   WildFly {wildflyVersion} offers two administrative mechanisms for managing your
   running instance:
   
  -* web-based Administration Console
  -* command-line interface
  -
  -===== Authentication
  -
  -By default WildFly {wildflyVersion} is now distributed with security enabled for the
  -management interfaces, this means that before you connect using the
  +* a web-based Administration Console
  +* a command-line interface
  +
  +The link:Admin_Guide{outfilesuffix}[Admin Guide] covers the details on managing your WildFly
  +installation. Here we'll just touch on some of the basics.
  +
  +=== Authentication
  +
  +By default WildFly {wildflyVersion} is distributed with security enabled for the
  +management interfaces. This means that before you connect using the
   administration console or remotely using the CLI you will need to add a
  -new user, this can be achieved simply by using the _add-user.sh_ script
  +new user. This can be achieved simply by using the _add-user.sh_ script
   in the bin folder.
   
   After starting the script you will be guided through the process to add
  
positive.code: find your way around when it comes to deploying your own applications.
  
  [[wildfly-directory-structure]]
  ==== WildFly Directory Structure
  
  [cols=",",options="header"]
  |=======================================================================
  
negative.code: subsystems you want to add, remove, or modify.
  
  [[test-your-installation]]
  === Test Your Installation
  
  After executing one of the above commands, you should see output similar
  to what's shown below.
  