fix typo I found in this repo

Signed-off-by: Aaron.L.Xu <likexu@harmonycloud.cn>
This commit is contained in:
Aaron.L.Xu 2017-01-20 01:18:18 +08:00
parent 0a58d55e63
commit 08bcbddb32
11 changed files with 16 additions and 16 deletions

View file

@ -40,7 +40,7 @@ may be exported for access via corresponding _services_.
## Modules
In addition to the subsystems have, we have sevaral components that may cross
In addition to the subsystems have, we have several components that may cross
subsystem boundaries, referened to as components. We have the following
components:
@ -71,7 +71,7 @@ is a diagram illustrating the data flow for bundle creation.
Let's take pulling an image as a demonstrated example:
1. Instruct the Distribution layer to pull a particuler image. The distribution
1. Instruct the Distribution layer to pull a particular image. The distribution
layer places the image content into the _content store_. The image name and
root manifest pointers are registered with the metadata store.
2. Once the image is pulled, the user can instruct the bundle controller to

View file

@ -32,7 +32,7 @@ graphdrivers, minimizing the need to new code and sprawling tests.
## Scope
In the past, the `graphdriver` component has provided quite a lot of
funcionality in Docker. This includes serialization, hashing, unpacking,
functionality in Docker. This includes serialization, hashing, unpacking,
packing, mounting.
This _snapshot manager_ will only provide mount-oriented snapshot
@ -49,7 +49,7 @@ abstract, layer-based filesystems. The model works by building up sets of
directories with parent-child relationships, known as _Snapshots_.
Every snapshot is represented by an opaque `diff` directory, which acts as a
handle to the snapshot. It may contain driver specifc data, including changeset
handle to the snapshot. It may contain driver specific data, including changeset
data, parent information and arbitrary metadata.
The `diff` directory for a _snapshot_ is created with a transactional