Documentation fixes, given by Abhilash Raj.

4 files changed, 12 insertions, 13 deletions

diff --git a/src/mailman/docs/8-miles-high.rst b/src/mailman/docs/8-miles-high.rst
index 85b186fc5..ae3074e1c 100644
--- a/src/mailman/docs/8-miles-high.rst
+++ b/src/mailman/docs/8-miles-high.rst
@@ -162,9 +162,9 @@ when the Mailman daemon starts, and what queue the Runner manages.
 Shell Commands
 ==============
 
-`bin/mailman`: This is an ubercommand, with subcommands for all the various
-things admins might want to do, similar to Mailman 2's mailmanctl, but with
-more functionality.
+`mailman`: This is an ubercommand, with subcommands for all the various things
+admins might want to do, similar to Mailman 2's mailmanctl, but with more
+functionality.
 
 `bin/master`: The runner manager: starts, watches, stops the runner
 daemons.
diff --git a/src/mailman/docs/DEVELOP.rst b/src/mailman/docs/DEVELOP.rst
index f1225658e..5b3ee602a 100644
--- a/src/mailman/docs/DEVELOP.rst
+++ b/src/mailman/docs/DEVELOP.rst
@@ -72,10 +72,10 @@ queue.  You can think of these as fairly typical server process, and examples
 include the LMTP server, and the HTTP server for processing REST commands.
 
 All of the runners are managed by a *master watcher* process.  When you type
-``bin/mailman start`` you are actually starting the master.  Based on
+``mailman start`` you are actually starting the master.  Based on
 configuration options, the master will start the appropriate runners as
 subprocesses, and it will watch for the clean exiting of these subprocesses
-when ``bin/mailman stop`` is called.
+when ``mailman stop`` is called.
 
 
 Rules and chains
diff --git a/src/mailman/docs/MTA.rst b/src/mailman/docs/MTA.rst
index 1bc9c6c13..a10c8f3cf 100644
--- a/src/mailman/docs/MTA.rst
+++ b/src/mailman/docs/MTA.rst
@@ -143,7 +143,7 @@ Transport maps
 
 By default, Mailman works well with Postfix transport maps as a way to deliver
 incoming messages to Mailman's LMTP server.  Mailman will automatically write
-the correct transport map when its ``bin/mailman aliases`` command is run, or
+the correct transport map when its ``mailman aliases`` command is run, or
 whenever a mailing list is created or removed via other commands.  To connect
 Postfix to Mailman's LMTP server, add the following to Postfix's ``main.cf``
 file::
diff --git a/src/mailman/docs/START.rst b/src/mailman/docs/START.rst
index ae4fe43a5..3ca4460b4 100644
--- a/src/mailman/docs/START.rst
+++ b/src/mailman/docs/START.rst
@@ -188,14 +188,13 @@ The first existing file found wins.
  * ``/etc/mailman.cfg``
  * ``argv[0]/../../etc/mailman.cfg``
 
-Run the ``bin/mailman info`` command to see which configuration file Mailman
-will use, and where it will put its database file.  The first time you run
-this, Mailman will also create any necessary run-time directories and log
-files.
+Run the ``mailman info`` command to see which configuration file Mailman will
+use, and where it will put its database file.  The first time you run this,
+Mailman will also create any necessary run-time directories and log files.
 
-Try ``bin/mailman --help`` for more details.  You can use the commands
-``bin/mailman start`` to start the runner subprocess daemons, and of course
-``bin/mailman stop`` to stop them.
+Try ``mailman --help`` for more details.  You can use the commands
+``mailman start`` to start the runner subprocess daemons, and of course
+``mailman stop`` to stop them.
 
 Postorius, a web UI for administration and subscriber settings, is being
 developed as a separate, Django-based project.  For now, the most flexible