aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorJames Turnbull <james@lovedthanlost.net>2015-06-29 15:16:01 -0400
committerJames Turnbull <james@lovedthanlost.net>2015-06-29 15:16:01 -0400
commit77396bd66acc141f1d5a1743cecd27777af7ef1d (patch)
tree6d57825a7c7fdb6ef942d19f8bc6718b52b565cb /README.md
parent4fd284bde00f863d4d8b4196e38eb3fb5299805b (diff)
parent9030f531659ddc9ca7bfffcb708cde579973e2ae (diff)
Merge pull request #14222 from erikdw/fix-casing-of-vmware-in-main-doc
Use proper casing for VMware in README
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 381fe1f483..01e8a5c018 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ security@docker.com and not by creating a github issue.
A common method for distributing applications and sandboxing their
execution is to use virtual machines, or VMs. Typical VM formats are
-VMWare's vmdk, Oracle VirtualBox's vdi, and Amazon EC2's ami. In theory
+VMware's vmdk, Oracle VirtualBox's vdi, and Amazon EC2's ami. In theory
these formats should allow every developer to automatically package
their application into a "machine" for easy distribution and deployment.
In practice, that almost never happens, for a few reasons: