upstream/packer
1
0
Fork 0
mirror of https://github.com/hashicorp/packer.git synced 2026-06-09 00:32:09 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

small typo: either rather than ether on why page

Browse source
This commit is contained in:
Gareth Rushgrove 2013-06-28 17:24:24 +01:00
parent 7cf21dd98d
commit 2c24ab3e16
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/source/intro/why.html.markdown
View file

@ -10,7 +10,7 @@ next_title: "Packer Use Cases"
Pre-baked machine images have a lot of advantages, but most have been unable
to benefit from them because images have been too tedious to create and manage.
There were ether no existing tools to automate the creation of machine images or
There were either no existing tools to automate the creation of machine images or
they had too high of a learning curve. The result is that, prior to Packer,
creating machine images threatened the agility of operations teams, and therefore
aren't used, despite the massive benefits.