Clean up remaining "here" links in docs

Our docs Style Guide and rules would have us use link text that is more
helpful than simply here as a link.

doc/common_installation_problems/README.md

@@ -326,7 +326,7 @@ Expected process to exit with [0], but received '255'
 This is unlikely to happen with non virtualized machines but on a VPS with virtualization like openVZ, container might not have the required module enabled
 or container doesn't have access to kernel parameters.
-Try enabling the module on which sysctl errored out, on how to enable the module see example [here](https://serverfault.com/questions/477718/sysctl-p-etc-sysctl-conf-returns-error).
+Try [enabling the module](https://serverfault.com/questions/477718/sysctl-p-etc-sysctl-conf-returns-error) on which sysctl errored out.
 There is a reported workaround described in [this issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/361) which requires editing the GitLab' internal recipe by supplying the switch which will ignore failures. Ignoring errors can have unexpected side effects on performance of your GitLab server so it is not recommended to do so.
@@ -470,7 +470,7 @@ sudo chown -R git:git /var/opt/gitlab/gitlab-rails/tmp/cache
 ## 'Short read or OOM loading DB' error
-Try cleaning the old Redis session by following the [documentation here.](https://docs.gitlab.com/ee/operations/cleaning_up_redis_sessions.html)
+Try [cleaning the old Redis session](https://docs.gitlab.com/ee/operations/cleaning_up_redis_sessions.html).
 ## Apt error 'The requested URL returned error: 403'

doc/settings/configuration.md

@@ -562,8 +562,7 @@ Run `sudo gitlab-ctl reconfigure` for the settings to take effect.
 ## Configuring Rack Attack
 To prevent abusive clients from doing damage, GitLab uses the Rack Attack gem.
-Check [this page](https://docs.gitlab.com/ee/security/rack_attack.html)
-for more information.
+Learn how to [configure Rack Attack](https://docs.gitlab.com/ee/security/rack_attack.html).
 ## Disabling automatic cache cleaning during installation
@@ -604,8 +603,8 @@ Disabling impersonation is documented in
 ## Error Reporting and Logging with Sentry
 [Sentry](https://sentry.io) is an error reporting and logging tool which can be
-used as SaaS or on premise. It's Open Source and you can browse its source code
-repositories [here](https://github.com/getsentry).
+used as SaaS or on premise. It's Open Source, and you can [browse its source code
+repositories](https://github.com/getsentry).
 The following settings can be used to configure Sentry: