Fix URLs to picl-k3os-image-generator project

These need to point to my fork for the time being because the changes
haven’t been upstreamed yet.

README.md

@@ -16,7 +16,7 @@ That Kubernetes operator doesn't exist. At least, it didn't until now. 🤠
 ## Prerequisites
 
 1. A k3OS cluster that's running [nominally](https://joshdance.medium.com/what-does-nominal-mean-when-spacex-mission-control-says-it-39c2d249da27#:~:text=performing%20or%20achieved%20within%20expected,within%20expected%20and%20acceptable%20limits.).
-2. A local clone of https://github.com/sgielen/picl-k3os-image-generator.
+2. A local clone of https://github.com/annismckenzie/picl-k3os-image-generator (my fork).
 3. The `config` directory with YAML files as describes in https://github.com/sgielen/picl-k3os-image-generator#getting-started:
 ```
 ├── config
@@ -25,7 +25,8 @@ That Kubernetes operator doesn't exist. At least, it didn't until now. 🤠
 │  └── dc:a6:32:xx:xx:xx.yaml
 ```
 3. Your local `kubectl` configured to push YAMLs to your k3OS cluster.
-4. Execute `make deploy-k3os-config` in your local checkout of `picl-k3os-image-generator`. This will generate the configuration and push it into the cluster.
+4. Execute `make update-k3osconfig-secret` in your local checkout of `picl-k3os-image-generator` to validate the YAML files in the `config` directory and to generate the secret for the operator.
+5. Execute `make deploy-k3os-config` in your local checkout of `picl-k3os-image-generator`. This will generate the configuration and push it into the cluster.
 5. Continue on with the installation steps outlined below.