anchor.diff:  RuboCop server starting on 127.0.0.1:55822.
   ```
   
  -This may be supported so that no reboot is required in future.
  -
   == Command Line Options
   
  -These are options for server operations.
  +These are the command-line options for server operations:
   
  -* `--server` ... If server process has not started yet, start the
  +* `--server` ... If a server process has not been started yet, start the
   server process and execute inspection with server. You can specify
  -the server host and port with the $RUBOCOP_SERVER_HOST and
  -the $RUBOCOP_SERVER_PORT environment variables.
  -* `--no-server` ... If server process has been started, stop the
  -server process and execute inspection with server.
  +the server host and port with the `$RUBOCOP_SERVER_HOST` and
  +the `$RUBOCOP_SERVER_PORT` environment variables.
  +* `--no-server` ... If a server process has been started, stop the
  +server process and execute inspection without the server.
   * `--restart-server` ... Restart server process.
   * `--start-server` ... Start server process.
   * `--stop-server` ... Stop server process.
  
positive.code: 
  NOTE: The `rubocop` command is executed using server process if server is started.
  Whenever server process is not running, it will load the RuboCop runtime files and execute.
  (same behavior as 1.30 and lower)
  
  If server is already running, just display the PID. The new server will not start.
  
  ```console
  % rubocop --start-server
  RuboCop server (16060) is already running.
  ```
  
  A started server process name is `rubocop --server` with project directory path.
  
  ```console
  % ps aux | grep 'rubocop --server'
  
negative.code: == Restart Server
  
  The started server does not reload the configuration file.
  You will need to restart the server when you upgrade RuboCop or change
  the RuboCop configuration.
  
  ```console
  