diff --git a/docs/features/traffic-management/alb.md b/docs/features/traffic-management/alb.md
index 291a56d4e3..5530d27ea2 100644
--- a/docs/features/traffic-management/alb.md
+++ b/docs/features/traffic-management/alb.md
@@ -138,7 +138,7 @@ spec:
 By default, a rollout will inject the `alb.ingress.kubernetes.io/actions.<SERVICE-NAME>` annotation
 using the service/action name specified under `spec.strategy.canary.stableService`. However, it may
 be desirable to specify an explicit service/action name different from the `stableService`. For
-example, [one pattern](/best-practices/#ingress-desiredstable-host-routes) is to use a single
+example, [one pattern](/argo-rollouts/best-practices/#ingress-desiredstable-host-routes) is to use a single
 Ingress containing three different rules to reach the canary, stable, and root service separately
 (e.g. for testing purposes). In this case, you may want to specify a "root" service as the
 service/action name instead of stable. To do so, reference a service under `rootService` under the
diff --git a/examples/helm-blue-green/README.md b/examples/helm-blue-green/README.md
index 2091c7a0b0..d8f1a102ba 100644
--- a/examples/helm-blue-green/README.md
+++ b/examples/helm-blue-green/README.md
@@ -5,7 +5,7 @@ regardless of the event source. If you package your manifest
 with the Helm package manager you can perform Progressive Delivery deployments with Helm
 
 1. Install the Argo Rollouts controller in your cluster: https://github.com/argoproj/argo-rollouts#installation
-2. Instal the `helm` executable locally: https://helm.sh/docs/intro/install/
+2. Install the `helm` executable locally: https://helm.sh/docs/intro/install/
 
 ## Deploying the initial version