From 8ce64b200080a80d417b6c041394bdf021dd4b58 Mon Sep 17 00:00:00 2001 From: fate-grand-order Date: Fri, 10 Feb 2017 10:52:25 +0800 Subject: [PATCH] fix some typos Signed-off-by: fate-grand-order --- design/architecture.md | 2 +- design/lifecycle.md | 2 +- design/mounts.md | 2 +- events/events_test.go | 2 +- events/transaction.go | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/design/architecture.md b/design/architecture.md index fc6d23671..0c3196580 100644 --- a/design/architecture.md +++ b/design/architecture.md @@ -41,7 +41,7 @@ may be exported for access via corresponding _services_. ## Modules In addition to the subsystems have, we have several components that may cross -subsystem boundaries, referened to as components. We have the following +subsystem boundaries, referenced to as components. We have the following components: - __*Executor*__: The executor implements the actual container runtime. diff --git a/design/lifecycle.md b/design/lifecycle.md index c7896e20e..6ab44bf16 100644 --- a/design/lifecycle.md +++ b/design/lifecycle.md @@ -5,7 +5,7 @@ While containerd is a daemon that provides API to manage multiple containers, th ## containerd -The daemon provides an API to manage multiple containers. It can handle locking in process where needed to cordinate tasks between subsystems. While the daemon does fork off the needed processes to run containers, the shim and runc, these are re-parented to the system's init. +The daemon provides an API to manage multiple containers. It can handle locking in process where needed to coordinate tasks between subsystems. While the daemon does fork off the needed processes to run containers, the shim and runc, these are re-parented to the system's init. ## shim diff --git a/design/mounts.md b/design/mounts.md index 215c23fae..ab3760c0d 100644 --- a/design/mounts.md +++ b/design/mounts.md @@ -13,7 +13,7 @@ unit and unmounted as a unit. From an architecture perspective, components produce mounts and runtime executors consume them. -More imaginitive use cases include the ability to virtualize a series of mounts +More imaginative use cases include the ability to virtualize a series of mounts from various components without ever having to create a runtime. This will aid in testing and implementation of satellite components. diff --git a/events/events_test.go b/events/events_test.go index 88281ead7..c58fc6225 100644 --- a/events/events_test.go +++ b/events/events_test.go @@ -22,7 +22,7 @@ func TestBasicEvent(t *testing.T) { ctx = WithTopic(ctx, "content") // simulate sub-operations with a separate topic, on the content store - G(ctx).Post(ctx, fmt.Sprintf("received sha:256")) + G(ctx).Post(ctx, fmt.Sprint("received sha:256")) G(ctx).Post(ctx, fmt.Sprintf("unpack layer %v", layer)) diff --git a/events/transaction.go b/events/transaction.go index c314d6104..11a2cd40b 100644 --- a/events/transaction.go +++ b/events/transaction.go @@ -37,7 +37,7 @@ func (tx *transaction) begin(ctx context.Context, poster Poster) *transaction { } // post the transaction started event - poster.Post(ctx, child.makeTransactionEvent("begin")) // tranactions are really just events + poster.Post(ctx, child.makeTransactionEvent("begin")) // transactions are really just events return child }