From bffa20d6bb5948c20df02536ff5c85d61f6db230 Mon Sep 17 00:00:00 2001 From: Richard Scothern Date: Fri, 31 Jul 2015 16:43:01 -0700 Subject: [PATCH] Spelling corrections Signed-off-by: Richard Scothern --- docs/spec/api.md.tmpl | 6 +++--- registry/api/v2/descriptors.go | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/spec/api.md.tmpl b/docs/spec/api.md.tmpl index de2f5a90..cc6bd7c5 100644 --- a/docs/spec/api.md.tmpl +++ b/docs/spec/api.md.tmpl @@ -277,7 +277,7 @@ API. When this header is omitted, clients may fallback to an older API version. This API design is driven heavily by [content addressability](http://en.wikipedia.org/wiki/Content-addressable_storage). The core of this design is the concept of a content addressable identifier. It -uniquely identifies content by taking a collision-resistent hash of the bytes. +uniquely identifies content by taking a collision-resistant hash of the bytes. Such an identifier can be independently calculated and verified by selection of a common _algorithm_. If such an identifier can be communicated in a secure manner, one can retrieve the content from an insecure source, calculate it @@ -791,7 +791,7 @@ Images are stored in collections, known as a _repository_, which is keyed by a contain several repositories. The list of available repositories is made available through the _catalog_. -The catalog for a given registry can be retrived with the following request: +The catalog for a given registry can be retrieved with the following request: ``` GET /v2/_catalog @@ -875,7 +875,7 @@ To get the next result set, a client would issue the request as follows, using the URL encoded in the described `Link` header: ``` -GET /v2/_catalog?n=&last= +GET /v2/_catalog?n=&last= ``` The above process should then be repeated until the `Link` header is no longer diff --git a/registry/api/v2/descriptors.go b/registry/api/v2/descriptors.go index 74bdb9f2..67b5c129 100644 --- a/registry/api/v2/descriptors.go +++ b/registry/api/v2/descriptors.go @@ -536,7 +536,7 @@ var routeDescriptors = []RouteDescriptor{ }, Successes: []ResponseDescriptor{ { - Description: "The manifest idenfied by `name` and `reference`. The contents can be used to identify and resolve resources required to run the specified image.", + Description: "The manifest identified by `name` and `reference`. The contents can be used to identify and resolve resources required to run the specified image.", StatusCode: http.StatusOK, Headers: []ParameterDescriptor{ digestHeader, @@ -928,7 +928,7 @@ var routeDescriptors = []RouteDescriptor{ { Name: RouteNameBlobUpload, Path: "/v2/{name:" + RepositoryNameRegexp.String() + "}/blobs/uploads/", - Entity: "Intiate Blob Upload", + Entity: "Initiate Blob Upload", Description: "Initiate a blob upload. This endpoint can be used to create resumable uploads or monolithic uploads.", Methods: []MethodDescriptor{ {