diff --git a/cmd/kops/util/factory.go b/cmd/kops/util/factory.go
index e368f57fd6..75d9210222 100644
--- a/cmd/kops/util/factory.go
+++ b/cmd/kops/util/factory.go
@@ -53,12 +53,12 @@ func NewFactory(options *FactoryOptions) *Factory {
 
 const (
 	STATE_ERROR = `Please set the --state flag or export KOPS_STATE_STORE.
-A valid value follows the format s3://<bucket>.
-A s3 bucket is required to store cluster state information.`
+For example, a valid value follows the format s3://<bucket>.
+You can find the supported stores in https://github.com/kubernetes/kops/blob/master/docs/state.md.`
 
-	INVALID_STATE_ERROR = `Unable to read state store s3 bucket.
-Please use a valid s3 bucket uri when setting --state or KOPS_STATE_STORE env var.
-A valid value follows the format s3://<bucket>.
+	INVALID_STATE_ERROR = `Unable to read state store.
+Please use a valid state store when setting --state or KOPS_STATE_STORE env var.
+For example, a valid value follows the format s3://<bucket>.
 Trailing slash will be trimmed.`
 )
 
diff --git a/docs/philosophy.md b/docs/philosophy.md
index 80aa973169..2f5b3cd2f9 100644
--- a/docs/philosophy.md
+++ b/docs/philosophy.md
@@ -32,9 +32,7 @@ There are two primary types:
 
 ## State Store
 
-The API objects are currently stored in an abstraction called a "state store", and currently the only implemented
-storage is an S3 bucket.  The storage of files in the S3 bucket is an implementation detail.  Expect more state
-stores soon.  For example, it might be convenient to put the InstanceGroup into the kubernetes API itself.
+The API objects are currently stored in an abstraction called a "state store".  [state.md](/docs/state.md) has more detail.
 
 ## Configuration inference
 
@@ -53,4 +51,4 @@ single source of truth and it is practical to implement alternatives to nodeup &
 such as kubelet might read their configuration directly from the state store in future, eliminating the need to
 have a management process that copies values around.
 
-Currently the 'completed' cluster specification is stored in the state store in a file called `cluster.spec`
\ No newline at end of file
+Currently the 'completed' cluster specification is stored in the state store in a file called `cluster.spec`