Update faasd links

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

docs/architecture/invocations.md

@@ -4,7 +4,7 @@ This page aims to explain function invocations and lifecycle.
 
 In an OpenFaaS installation, functions can be invoked through HTTP requests to the OpenFaaS gateway, specifying the path as part of the URL.
 
-There are some differences between OpenFaaS with [Kubernetes](/deployment/kubernetes) and [faasd](/deployment/faasd), so this page focuses on users of Kubernetes.
+There are some differences between OpenFaaS with [Kubernetes](/deployment/kubernetes) and [faasd](/deployment/edge), so this page focuses on users of Kubernetes.
 
 ![Conceptual diagram: a synchronous invocation](/images/invoke.png)
 > Conceptual diagram: a synchronous invocation.

docs/architecture/stack.md

@@ -36,7 +36,7 @@ These applications can be installed via Helm charts, or by using a GitOps operat
 
 * The unit of execution for a function is a Pod, managed by containerd or Docker.
 * A container registry holds each function as an immutable artifact that can be deployed to the OpenFaaS gateway using its REST API, UI or CLI.
-* Kubernetes is the platform that allows functions to scale across multiple hosts, [faasd](/deployment/faasd/) is a simpler alternative for smaller installations.
+* Kubernetes is the platform that allows functions to scale across multiple hosts, [faasd](/deployment/edge/) is a simpler alternative for smaller installations.
 
 This layer is usually built manually during exploration and development, and using a tool like Terraform for production.
 

docs/cli/secrets.md

@@ -2,7 +2,7 @@
 
 The OpenFaaS CLI allows you to create, update, list and delete secrets using `faas-cli` instead of Docker or Kubernetes command line tools.
 
-The reason behind this is to give you simplicity when you need to use secrets for your functions as well as to provide a layer of abstraction, as it will work for both Kubernetes and [faasd](/deployment/faasd/).
+The reason behind this is to give you simplicity when you need to use secrets for your functions as well as to provide a layer of abstraction, as it will work for both Kubernetes and [faasd](/deployment/edge/).
 
 See also: `faas-cli secret --help`