Fixes for local GitHub cache instructions

- Fix link to registry mirror page
- Fix typo in instructions to create /etc/seaweedfs/s3.conf

Signed-off-by: Han Verstraete (OpenFaaS Ltd) <[email protected]>

docs/tasks/local-github-cache.md

@@ -1,6 +1,6 @@
 # Run a local GitHub Cache
 
-The cache for GitHub Actions can speed up CI/CD pipelines. Hosted runners are placed close to the cache which means the latency is very low. Self-hosted runners can also make good use of this cache. Just like caching container images on the host in (a registry mirror)[/tasks/registry-mirror/], you can also get a speed boost over the hosted cache by running your own cache directly on the host.
+The cache for GitHub Actions can speed up CI/CD pipelines. Hosted runners are placed close to the cache which means the latency is very low. Self-hosted runners can also make good use of this cache. Just like caching container images on the host in [a registry mirror](/tasks/registry-mirror/), you can also get a speed boost over the hosted cache by running your own cache directly on the host.
 
 To improve cache speeds with Actuated runners you can run a self-hosted S3 server and switch out the official [actions/cache@v3](https://github.com/actions/cache) with [tespkg/actions-cache@v1](https://github.com/tespkg/actions-cache). The tespkg/actions-cache@v1 can target S3 instead of the proprietary GitHub cache.
 
@@ -54,7 +54,7 @@ cat >> /tmp/s3.conf <<EOF
 }
 EOF
 
-mkldir -p /etc/seaweedfs
+mkdir -p /etc/seaweedfs
 sudo mv /tmp/s3.conf /etc/seaweedfs/s3.conf
 ```