TrueCloudLab/distribution
12
0
Fork 3
Code Issues 2 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Granmar and speeling fixes

Browse source 
Signed-off-by: Olivier Gambier <olivier@docker.com>
This commit is contained in:
Olivier Gambier 2015-08-28 12:46:09 -07:00
parent 6197ca7b10
commit 0c42f0cd63
4 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/building.md
View file

@ -22,7 +22,7 @@ OSX users who want to run natively can do so following [the instructions here](o
### Gotchas ### Gotchas
You are expected to know your way with go & git. You are expected to know your way around with go & git.
If you are a casual user with no development experience, and no preliminary knowledge of go, building from source is probably not a good solution for you. If you are a casual user with no development experience, and no preliminary knowledge of go, building from source is probably not a good solution for you.
@ -34,7 +34,7 @@ for proper setup. If done correctly, you should have a GOROOT and GOPATH set in
environment. environment.
If a Go development environment is setup, one can use `go get` to install the If a Go development environment is setup, one can use `go get` to install the
`registry` source code from the current latest: `registry` command from the current latest:
go get github.com/docker/distribution/cmd/registry go get github.com/docker/distribution/cmd/registry

2
docs/notifications.md
View file

@ -63,7 +63,7 @@ INFO[0000] configuring endpoint alistener (https://mylistener.example.com/event)
Events have a well-defined JSON structure and are sent as the body of Events have a well-defined JSON structure and are sent as the body of
notification requests. One or more events are sent in a structure called an notification requests. One or more events are sent in a structure called an
envelope. Each event has a unique id that can be used to uniquify incoming envelope. Each event has a unique id that can be used to uniquely identify incoming
requests, if required. Along with that, an _action_ is provided with a requests, if required. Along with that, an _action_ is provided with a
_target, identifying the object mutated during the event. _target, identifying the object mutated during the event.

2
docs/osx-setup-guide.md
View file

@ -2,7 +2,7 @@
+++ +++
title = "Running on OS X" title = "Running on OS X"
description = "Explains how to run a registry on OS X" description = "Explains how to run a registry on OS X"
keywords = ["registry, on-prem, images, tags, repository, distribution, osx, recipe, advanced"] keywords = ["registry, on-prem, images, tags, repository, distribution, OS X, recipe, advanced"]
+++ +++
<![end-metadata]--> <![end-metadata]-->