fix: Architecture overview in KEDA HTTP blog post (kedacore#471)

Signed-off-by: Tom Kerkhove <[email protected]>

content/blog/announcing-http-add-on.md → content/blog/2021-06-24-announcing-http-add-on.md

@@ -40,7 +40,7 @@ The system is made up of 3 components:
 - **External scaler**: This is an [external push scaler](https://keda.sh/docs/2.1/scalers/external-push/) that constantly pings the interceptor to get pending HTTP queue metrics. It transforms these data and sends them directly down to KEDA, which then makes a scaling decision
 - **Operator**:  This is an [Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that runs for the convenience of the user. It listens for new [CRD](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) resources, called `HTTPScaledObject`s, and creates and configures interceptors and scalers so that your existing [`Deployment`](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) will begin autoscaling according to incoming HTTP traffic.
 
-![architecture diagram](/static/img/blog/http-add-on/arch.png)
+![architecture diagram](/img/blog/http-add-on/arch.png)
 
 ## Seeing it in action