nit: Add space to feature support docs
Change-Id: I13c5f9c053f848facbcbd663fc677f4f991d7105
This commit is contained in:
parent
b8d751c67b
commit
7ba9b8143c
@ -10,7 +10,7 @@ following general guiding principles were applied
|
||||
|
||||
* **Inclusivity** - people have shown ability to make effective
|
||||
use of a wide range of virtualization technologies with broadly
|
||||
varying featuresets. Aiming to keep the requirements as inclusive
|
||||
varying feature sets. Aiming to keep the requirements as inclusive
|
||||
as possible, avoids second-guessing what a user may wish to use
|
||||
the cloud compute service for.
|
||||
|
||||
@ -24,7 +24,7 @@ following general guiding principles were applied
|
||||
* **Competition** - an early leader in the cloud compute service space
|
||||
was Amazon EC2. A sanity check for whether a feature should be
|
||||
mandatory is to consider whether it was available in the first
|
||||
public release of EC2. This had quite a narrow featureset, but
|
||||
public release of EC2. This had quite a narrow feature set, but
|
||||
none the less found very high usage in many use cases. So it
|
||||
serves to illustrate that many features need not be considered
|
||||
mandatory in order to get useful work done.
|
||||
|
Loading…
Reference in New Issue
Block a user