update

Author: BolajiOlajide

docs/admin/deploy/docker-single-container/index.mdx

@@ -147,7 +147,7 @@ A [standard upgrade](/admin/updates/#standard-upgrades) occurs between two minor
 - Read our [update policy](/admin/updates/#update-policy) to learn about Sourcegraph updates.
 - Find the relevant entry for your update in the [update notes for single-container Sourcegraph with Docker](/admin/updates/server).
 
-To update, just use the newer `sourcegraph/server:N.N.N` Docker image (where `N.N.N` is a patch or single minor release away your current version) in place of the older one, using the same Docker volumes. Your server's data will be migrated automatically if needed. You can always find the version number details of the latest release via the [changelog](/technical-changelog).
+To update, just use the newer `sourcegraph/server:N.N.N` Docker image (where `N.N.N` is a patch or single minor release away your current version) in place of the older one, using the same Docker volumes. Your server's data will be migrated automatically if needed. You can always find the version number details of the latest release via the [technical changelog](/technical-changelog).
 
 ### Multi-version upgrades
 

docs/admin/deploy/machine-images/aws-ami.mdx

@@ -174,7 +174,7 @@ Now that your instance is confirmed to be working, and you have HTTPS working th
 
 Please take time to review the following before proceeding with the upgrades:
 
-- [Changelog](/technical-changelog)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 

docs/admin/deploy/machine-images/gce.mdx

@@ -132,7 +132,7 @@ As a result, setting up a static IP for your Sourcegraph instance is strongly re
 
 Please take time to review the following before proceeding with the upgrades:
 
-- [Changelog](/technical-changelog)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 - [Multi-version upgrade procedure](/admin/updates/kubernetes#multi-version-upgrade-procedure)

docs/admin/deploy/single-node/script.mdx

@@ -72,7 +72,7 @@ Sourcegraph will be available on ports 80 and 443 (using a self signed certifica
 We recommend deploying your own reverse proxy to terminate TLS connections with a properly signed certificate.
 
 ## Upgrade
-- [Changelog](/technical-changelog)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 - [Multi-version upgrade procedure](/admin/updates/kubernetes#multi-version-upgrade-procedure)

docs/admin/how-to/site-admin-quickstart.mdx

@@ -23,7 +23,7 @@ Regardless of the deployment option you choose, Sourcegraph can be self-hosted l
 
 
 ## Updating your instance
-New versions of Sourcegraph are released monthly (with patches released in between, as needed). New updates are announced in the [Sourcegraph blog](https://about.sourcegraph.com/blog), and comprehensive update notes are available in the [changelog](/technical-changelog).
+New versions of Sourcegraph are released monthly (with patches released in between, as needed). New updates are announced in the [Sourcegraph blog](https://about.sourcegraph.com/blog), and comprehensive update notes are available in the [technical changelog](/technical-changelog).
 
 To check the current version of your instance, go to **User menu > Site admin > Updates**.
 

docs/admin/updates/index.mdx

@@ -4,7 +4,7 @@ This page is intended as an entry point into Sourcegraph versioning, upgrades, a
 
 **If you are already familiar with Sourcegraph upgrades [skip to instance specific procedures](#instance-specific-procedures).**
 
-> *Note: For product update notes, please refer to the [changelog](/technical-changelog).*
+> *Note: For product update notes, please refer to the [technical changelog](/technical-changelog).*
 
 ## General concepts