diff --git a/cassandra/image/cassandra.yaml b/cassandra/image/cassandra.yaml index f409e820..c5df4cad 100644 --- a/cassandra/image/cassandra.yaml +++ b/cassandra/image/cassandra.yaml @@ -506,7 +506,7 @@ tombstone_failure_threshold: 100000 # Increase if your rows are large, or if you have a very large # number of rows per partition. The competing goals are these: # 1) a smaller granularity means more index entries are generated -# and looking up rows withing the partition by collation column +# and looking up rows within the partition by collation column # is faster # 2) but, Cassandra will keep the collation index in memory for hot # rows (as part of the key cache), so a larger granularity means diff --git a/high-availability/provision.sh b/high-availability/provision.sh index dacfebdd..0cd7c943 100755 --- a/high-availability/provision.sh +++ b/high-availability/provision.sh @@ -90,7 +90,7 @@ function write_api_server_config { mkdir -p -m 777 /srv/kubernetes/ ### We will move files back and forth between the /srv/kube.. directory. - ### That is how we modulate leader. Each node will continously either + ### That is how we modulate leader. Each node will continuously either ### ensure that the manifests are in this dir, or else, are in the kubelet manifest dir. cp /vagrant/kube-scheduler.manifest /vagrant/kube-controller-manager.manifest /srv/kubernetes diff --git a/k8petstore/dev/README b/k8petstore/dev/README index 25c8d7b1..02ec1e4f 100644 --- a/k8petstore/dev/README +++ b/k8petstore/dev/README @@ -20,7 +20,7 @@ go get go run PetStoreBook.go ``` -Once the app works the way you want it to, test it in the vagrant recipe below. This will gaurantee that you're local environment isn't doing something that breaks the containers at the versioning level. +Once the app works the way you want it to, test it in the vagrant recipe below. This will guarantee that you're local environment isn't doing something that breaks the containers at the versioning level. ### Testing