Upgrade pgbouncer documentation

* Add link to components in HA README
* Fix typo in pgbouncer page

doc/administration/high_availability/README.md

@@ -33,10 +33,10 @@ cases components can be combined on the same nodes to reduce complexity.
 
 - Unicorn/Workhorse - Web-requests (UI, API, Git over HTTP)
 - Sidekiq - Asynchronous/Background jobs
-- PostgreSQL - Database
-  - Consul - Database service discovery and health checks/failover
-  - PGBouncer - Database pool manager
-- Redis - Key/Value store (User sessions, cache, queue for Sidekiq)
+- [PostgreSQL](database.md) - Database
+  - [Consul](consul.md) - Database service discovery and health checks/failover
+  - [PGBouncer](pgbouncer.md) - Database pool manager
+- [Redis](redis.md) - Key/Value store (User sessions, cache, queue for Sidekiq)
   - Sentinel - Redis health check/failover manager
 
 ## Architecture Examples

doc/administration/high_availability/pgbouncer.md

@@ -4,7 +4,7 @@
 
 As part of its High Availability stack, GitLab Premium includes a bundled version of [Pgbouncer](https://pgbouncer.github.io/) that can be managed through `/etc/gitlab/gitlab.rb`.
 
-In a High Availability setup, Pgbounce is used to seamlessly migrate database connections between servers in a failover scenario.
+In a High Availability setup, Pgbouncer is used to seamlessly migrate database connections between servers in a failover scenario.
 
 Additionally, it can be used in a non-HA setup to pool connections, speeding up response time while reducing resource usage.