docs: correct stale script and template references

cmd/kubectl-ate/README.md

@@ -79,7 +79,7 @@ Manage the execution state of your workloads.
 
 ```bash
 # Create a new actor deriving from a specific ActorTemplate
-kubectl ate create actor my-actor --template=ate-demo-counter/counter-template
+kubectl ate create actor my-actor --template=ate-demo-counter/counter
 
 # Resume an actor (assigns it to a free worker and restores its state)
 kubectl ate resume actor my-actor

cmd/servers/atenet/readme.md

@@ -38,5 +38,5 @@ RBAC permissions:
 
 ## testing
 
-hack/run-test.sh will execute a local smoke test with a fake ATE API server.
-This does not require any cluster and uses the fake ATE api server.
+Run the package tests with `go test ./cmd/servers/atenet/...`. Cluster e2e
+tests use the shared `hack/run-e2e.sh` runner.

demos/sandbox/README.md

@@ -16,7 +16,7 @@ It allows you to run arbitrary commands in an sandboxed, isolated container (run
 
 - A k8s cluster with Agent Substrate installed.
 - `ko` installed for building images.
-- A GCS bucket for storing snapshots (configured in `manifests/sandbox/sandbox.yaml`).
+- A GCS bucket for storing snapshots (configured in `manifests/sandbox/sandbox.yaml.tmpl`).
 - `kubectl-ate` CLI installed (can be installed via `go install ./cmd/kubectl-ate`).
 
 ## How to Run on Agent Substrate

internal/e2e/readme.md

@@ -18,7 +18,9 @@ $ go test -v ./internal/e2e/suites/... -args -e2e
 
 ## Preconditions
 
-The e2e tests assume you have a cluster setup with `hack/install.sh`.
+The e2e tests assume you have a cluster set up with Agent Substrate installed,
+for example via `hack/install-ate.sh --deploy-ate-system` or
+`hack/install-ate-kind.sh --deploy-ate-system`.
 
 ## Creating a new test suite