Update descriptions, remove $env, wording tweaks

Signed-off-by: Tim Hansen <timbonicus@gmail.com>

docs/integrations/gitlab/locations.md

@@ -2,11 +2,11 @@
 id: locations
 title: GitLab Locations
 sidebar_label: Locations
-description: Documentation on GitLab location integration
+description: Integrating source code stored in GitLab into the Backstage catalog
 ---
 
 The GitLab integration supports loading catalog entities from gitlab.com or a
-self-hosted GitLab. Components can be added to
+self-hosted GitLab. Entities can be added to
 [static catalog configuration](../../features/software-catalog/configuration.md),
 or registered with the
 [catalog-import](https://github.com/backstage/backstage/tree/master/plugins/catalog-import)
@@ -16,8 +16,7 @@ plugin.
 integrations:
   gitlab:
     - host: gitlab.com
-      token:
-        $env: GITLAB_TOKEN
+      token: ${GITLAB_TOKEN}
 ```
 
 > Note: A public GitLab provider is added automatically at startup for
@@ -29,9 +28,8 @@ can list the GitLab providers you want to fetch data from. Each entry is a
 structure with up to four elements:
 
 - `host`: The host of the GitLab instance, e.g. `gitlab.company.com`.
-- `token` (optional): An authentication token as expected by GitLab. If
-  supplied, it will be passed along with all calls to this provider, both API
-  and raw. If it is not supplied, anonymous access will be used.
+- `token` (optional): An authentication token as expected by GitLab. If this is
+  not supplied, anonymous access will be used.
 - `apiBaseUrl` (optional): The URL of the GitLab API. For self-hosted
   installations, it is commonly at `https://<host>/api/v4`. For gitlab.com, this
   configuration is not needed as it can be inferred.