Fix #3378. Update usage.md

docs/usage.md

@@ -1,7 +1,7 @@
 Usage
 -----------
 
-With the [Drush Launcher](https://github.com/drush-ops/drush-launcher), Drush can be run in your shell by typing "drush" from within your project root directory or anywhere within Drupal.
+Drush can be run in your shell by typing "drush" from within your project root directory or anywhere within Drupal.
 
     $ drush [options] <command> [argument1] [argument2]
 
@@ -16,20 +16,11 @@ For even more documentation, use the 'topic' command:
 Options
 -----------
 
-For multisite installations, use the --uri option to target a particular site.  If
-you are outside the Drupal web root, you will need to use the --root, --uri or other
-command line options just for Drush to work.
+For multisite installations, use a site alias or the --uri option to target a particular site.
 
-    $ drush --uri=http://example.com pm-enable
-
-If you wish to be able to select your Drupal site implicitly from the
-current working directory without using the --uri option, but you need your
-base_url to be set correctly, you may force it by setting the uri in
-a drush.yml file located in the same directory as your settings.php file.
-
-```
-uri: "http://example.com"
-```
+    $ drush --uri=http://example.com pm:enable
+
+If you are outside the Composer project and not using a site alias, you need to specify --root and --uri for Drush to locate and bootstrap the right Drupal site.
 
 Site Aliases
 ------------
@@ -43,7 +34,7 @@ $ drush @staging updatedb
 # Synchronize staging files to production
 $ drush rsync @staging:%files/ @live:%files
 # Synchronize database from production to dev, excluding the cache table
-$ drush sql-sync --structure-tables-key=custom @live @dev
+$ drush sql:sync --structure-tables-key=custom @live @dev
 ```
 
 See [example.site.yml](https://raw.githubusercontent.com/drush-ops/drush/master/examples/example.site.yml) for more information.