fixup! vendor: vendor.json cleanup

Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

vendor/github.com/docker/distribution/CHANGELOG.md

@@ -39,7 +39,7 @@
 - Changes the client Tags `All()` method to follow links
 - Allow registry clients to connect via HTTP2
 - Better handling of OAuth errors in client
-
+  
 #### Spec
 - Manifest: clarify relationship between urls and foreign layers
 - Authorization: add support for repository classes
@@ -104,3 +104,5 @@ The registry is go 1.7 compliant, and passes newer, more restrictive `lint` and
 
 #### Docker Image
 - Use Alpine Linux as base image
+
+

vendor/github.com/docker/distribution/RELEASE-CHECKLIST.md

@@ -25,7 +25,7 @@ check comment and correct commit hash.
 
 50. Push the signed tag
 
-60. Create a new [release](https://github.com/docker/distribution/releases).  In the case of a release candidate, tick the `pre-release` checkbox.
+60. Create a new [release](https://github.com/docker/distribution/releases).  In the case of a release candidate, tick the `pre-release` checkbox. 
 
 70. Update the registry binary in [distribution library image repo](https://github.com/docker/distribution-library-image) by running the update script and  opening a pull request.
 
@@ -41,3 +41,4 @@ e.g. to release `2.3.1`
    `2.3 -> 2.3.1`
 
 90. Build a new distribution/registry image on [Docker hub](https://hub.docker.com/u/distribution/dashboard) by adding a new automated build with the new tag and re-building the images.
+

vendor/github.com/docker/distribution/ROADMAP.md

@@ -27,7 +27,7 @@ considerations made in respect of the future of the project.
 Components of the Distribution Project are managed via github [milestones](https://github.com/docker/distribution/milestones). Upcoming
 features and bugfixes for a component will be added to the relevant milestone. If a feature or
 bugfix is not part of a milestone, it is currently unscheduled for
-implementation.
+implementation. 
 
 * [Registry](#registry)
 * [Distribution Package](#distribution-package)
@@ -40,7 +40,7 @@ The new Docker registry is the main portion of the distribution repository.
 Registry 2.0 is the first release of the next-generation registry. This was
 primarily focused on implementing the [new registry
 API](https://github.com/docker/distribution/blob/master/docs/spec/api.md),
-with a focus on security and performance.
+with a focus on security and performance. 
 
 Following from the Distribution project goals above, we have a set of goals
 for registry v2 that we would like to follow in the design. New features
@@ -105,9 +105,9 @@ landing in the registry.
 
 ##### Proxying to other Registries
 
-A _pull-through caching_ mode exists for the registry, but is restricted from
+A _pull-through caching_ mode exists for the registry, but is restricted from 
 within the docker client to only mirror the official Docker Hub.  This functionality
-can be expanded when image provenance has been specified and implemented in the
+can be expanded when image provenance has been specified and implemented in the 
 distribution project.
 
 ##### Metadata storage
@@ -247,13 +247,13 @@ Please see the following issues for more detail:
 - https://github.com/docker/distribution/issues/461
 - https://github.com/docker/distribution/issues/462
 
-### Distribution Package
+### Distribution Package 
 
 At its core, the Distribution Project is a set of Go packages that make up
 Distribution Components. At this time, most of these packages make up the
-Registry implementation.
+Registry implementation. 
 
-The package itself is considered unstable. If you're using it, please take care to vendor the dependent version.
+The package itself is considered unstable. If you're using it, please take care to vendor the dependent version. 
 
 For feature additions, please see the Registry section. In the future, we may break out a
 separate Roadmap for distribution-specific features that apply to more than
@@ -264,3 +264,4 @@ just the registry.
 ### Project Planning
 
 An [Open-Source Planning Process](https://github.com/docker/distribution/wiki/Open-Source-Planning-Process) is used to define the Roadmap. [Project Pages](https://github.com/docker/distribution/wiki) define the goals for each Milestone and identify current progress.
+

vendor/github.com/docker/distribution/registry/api/v2/errors.go

@@ -98,7 +98,7 @@ var (
 	ErrorCodeManifestBlobUnknown = errcode.Register(errGroup, errcode.ErrorDescriptor{
 		Value:   "MANIFEST_BLOB_UNKNOWN",
 		Message: "blob unknown to registry",
-		Description: `This error may be returned when a manifest blob is
+		Description: `This error may be returned when a manifest blob is 
 		unknown to the registry.`,
 		HTTPStatusCode: http.StatusBadRequest,
 	})