Fix broken links

explanation/performance.md

@@ -52,9 +52,9 @@ Also make sure that there is a stable network connection between the nodes of yo
 
 A very noticeable performance issue is a long wait time when starting an application.
 
-When a user starts an application, Anbox Cloud retrieves the application image and launches a new instance for it. By default, Anbox Cloud turns off image compression in LXD when launching an instance from an image. This method speeds up the launch of the instance (because the image does not need to be uncompressed), but it causes more traffic over the network (because the image is transferred uncompressed). If the network connection between your cluster nodes is rather slow, the overall instance startup time might improve by enabling image compression. You can change the default configuration by setting the [images_compression_algorithm](https://charmhub.io/ams-lxd/configure#images_compression_algorithm) configuration on the `ams-lxd` charm. Of course, in addition to compression, the size of the image is also relevant. The smaller the image, the faster it can be synchronised across the LXD nodes in a cluster.
+When a user starts an application, Anbox Cloud retrieves the application image and launches a new instance for it. By default, Anbox Cloud turns off image compression in LXD when launching an instance from an image. This method speeds up the launch of the instance (because the image does not need to be uncompressed), but it causes more traffic over the network (because the image is transferred uncompressed). If the network connection between your cluster nodes is rather slow, the overall instance startup time might improve by enabling image compression. You can change the default configuration by setting the [images_compression_algorithm](https://charmhub.io/ams-lxd/configuration#images_compression_algorithm) configuration on the `ams-lxd` charm. Of course, in addition to compression, the size of the image is also relevant. The smaller the image, the faster it can be synchronised across the LXD nodes in a cluster.
 
-Another configuration that affects the instance startup time is [shiftfs_enabled](https://charmhub.io/ams-lxd/configure#shiftfs_enabled). This configuration is currently disabled by default, because it can cause issues with some Android applications. However, if your applications run fine with `shiftfs_enabled` set, it can considerably improve the instance startup time. You should be aware though that support for shiftfs might be dropped in future releases.
+Another configuration that affects the instance startup time is [shiftfs_enabled](https://charmhub.io/ams-lxd/configuration#shiftfs_enabled). This configuration is currently disabled by default, because it can cause issues with some Android applications. However, if your applications run fine with `shiftfs_enabled` set, it can considerably improve the instance startup time. You should be aware though that support for shiftfs might be dropped in future releases.
 
 You should also check the hooks that you use in your application. If you use any startup hooks (`pre-start` or `post-start`) that take a long time or wait for resources to become available, the instance startup is delayed. If you use a `post-stop` hook that prolongs the shutdown of an instance, this might also affect the startup time of new instances (because it might not be possible to start more instances until the existing instances terminate).
 

howto/install/deploy-bare-metal.md

@@ -94,7 +94,7 @@ There are different ways of configuring a dedicated block storage device:
 
 ### Existing storage pool
 
-To use an existing LXD storage pool, set the [`storage_pool`](https://charmhub.io/ams/configure#storage_pool) configuration on the AMS charm to the name of the LXD storage pool that you want Anbox Cloud to use.
+To use an existing LXD storage pool, set the [`storage_pool`](https://charmhub.io/ams/configuration#storage_pool) configuration on the AMS charm to the name of the LXD storage pool that you want Anbox Cloud to use.
 
 For example, to use an existing LXD storage pool with the name `my-zfs-pool`, use an overlay file with the following content:
 
@@ -111,7 +111,7 @@ The LXD storage pool must use the ZFS storage driver. Other storage drivers are
 
 ### Dedicated storage device
 
-To use a dedicated storage device that is not defined by Juju for LXD storage, set the [`storage_device`](https://charmhub.io/ams/configure#storage_device) configuration on the AMS charm to the path of the storage device.
+To use a dedicated storage device that is not defined by Juju for LXD storage, set the [`storage_device`](https://charmhub.io/ams/configuration#storage_device) configuration on the AMS charm to the path of the storage device.
 
 For example, to use `/dev/sdb` as the dedicated storage device, use an overlay file with the following content:
 

howto/update/control-updates.md

@@ -10,5 +10,5 @@ In a production environment, this update behaviour might cause problems in some
 - Different nodes of an Anbox Cloud or LXD cluster might end up running different snap versions.
 
 To prevent such problems, use either of the following methods:
-* Define maintenance windows in which your systems can be updated without interrupting operations. See [Managing updates](https://snapcraft.io/docs/keeping-snaps-up-to-date) in the snap documentation for information on how to control snap updates on your systems.
+* Define maintenance windows in which your systems can be updated without interrupting operations. See [Managing updates](https://snapcraft.io/docs/managing-updates) in the snap documentation for information on how to control snap updates on your systems.
 * Configure a [Snap Store Proxy](https://docs.ubuntu.com/snap-store-proxy/) to control which snaps are served to the machines that use the proxy. In particular, you can use the proxy to [override snap revisions](https://docs.ubuntu.com/snap-store-proxy/en/overrides). In this method, you have full control over when snaps are updated.

reference/release-notes/1.16.3.md

@@ -11,7 +11,7 @@ Grafana Labs has published [a note](https://grafana.com/blog/2023/01/12/grafana-
 
 If the user chooses to add support for monitoring during the initialisation of the Anbox Cloud Appliance, the appliance installs Grafana and pins the APT signing key internally. This is needed to detect changes in the repository signature and to fail installation if the provided signature is not correct. Due to this, all new installations and updates of existing installations will fail until the new signing key is installed. The 1.16.3 release of the Anbox Cloud Appliance pins the new signing key from Grafana Labs, allowing installation and updates for Grafana again.
 
-If you deployed the regular Anbox Cloud and installed [the Grafana charm yourself](https://charmhub.io/grafana), update the [`install_keys` configuration item](https://charmhub.io/grafana/configure#install_keys) to provide the new GPG signing key to the installation.
+If you deployed the regular Anbox Cloud and installed [the Grafana charm yourself](https://charmhub.io/grafana), update the [`install_keys` configuration item](https://charmhub.io/grafana/configuration#install_keys) to provide the new GPG signing key to the installation.
 
 Please see the {ref}`ref-component-versions` for a list of updated components.
 

reference/release-notes/1.18.2.md

@@ -12,7 +12,7 @@ Please see {ref}`ref-component-versions` for a list of updated components.
 * The Android WebView has been updated to 114.0.5735.131.
 
 ## Important notes
-For 1.18.2 version and later, if you have a load balancer with proper TLS certificates placed in front of the Anbox stream agent and if you have set the [`location`](https://charmhub.io/anbox-stream-agent/configure#location) of the Anbox stream agent, TLS pinning must be disabled by running:
+For 1.18.2 version and later, if you have a load balancer with proper TLS certificates placed in front of the Anbox stream agent and if you have set the [`location`](https://charmhub.io/anbox-stream-agent/configuration#location) of the Anbox stream agent, TLS pinning must be disabled by running:
 
 ```
 juju config anbox-stream-agent tls_use_pinning=false