Merge lp:~stephen-stewart/snappy/fix-typos-in-config-docs into lp:~snappy-dev/snappy/snappy-moved-to-github

[Stephen Stewart]

fix typos

[lp:~stephen-stewart/snappy/fix-typos-in-config-docs]

456. By Stephen Stewart on 2015-05-13

remove double space

[John Lenton (chipaca)]

Also some polish! thanks :)

review: Approve

=== modified file 'docs/config.md'
--- docs/config.md	2015-04-22 13:08:08 +0000
+++ docs/config.md	2015-05-13 17:14:50 +0000
@@ -3,13 +3,13 @@
 
 The snappy config command is a mechanism for package to provide a way
 to set and get its configuration.  A standard yaml based protocol is
-used for the interaction. The application is repsonsible to provide a
-configuration handler that can transform yaml into the apps native
+used for the interaction. The application is responsible for providing
+a configuration handler that can transform yaml into the app's native
 configuration format.
 
-We plan to support a schema file for the yaml as well to make e.g. web
-based editing of the config simpler.  The format of the configuration
-is as follows:
+We plan also to support a schema file for the yaml to make editing
+simpler, for example web based editing of config. The format of the
+configuration is as follows:
 
 	config:
 	  packagename:
@@ -18,8 +18,8 @@
 	    key: value
 
 The application provides a configuration handler in
-meta/hooks/config. This configuration handler must provide reading new
-configuration from stdin and output the current configuration (after
+meta/hooks/config. This configuration handler must provide for reading
+new configuration from stdin and output the current configuration (after
 the new configuration has been applied) to stdout.
 
 The package config hook must return exitcode 0 and return valid yaml
@@ -39,16 +39,15 @@
  - error: optional error string
  - warning: optional warning string
 
-Some key/value pairs in the configuration are fixed and all
-applications. E.g. all applications that listen to a port must support
-the "ports" config option.
+Some key/value pairs in the configuration are fixed, for example all
+applications that listen to a port must support the "ports" config option.
 
-The current list of values that must be supported (if the feature is used:
+The current list of values that must be supported (if the feature is used):
 
  - ports: the listen ports (if the application listens to the network)
 
-When the configuratin is applied the service will be restarted by
-snappy automatically(?).
+When the configuration is applied the service will be restarted by
+snappy automatically.
 
 Examples:
 ---------
@@ -69,7 +68,7 @@
 
 Example to get a config:
 
-snappy calls meta/hooks/config with empty input. The meta/hooks/config sends 
+snappy calls meta/hooks/config with empty input. The meta/hooks/config sends
 the following back:
 
 	config:
@@ -82,17 +81,15 @@
 Example to set a non-existing config:
 
 snappy -> meta/hooks/config
-        
+
 	config:
 	  ubuntu-core:
 	    tea-in-the-morning: false
 
 meta/hooks/config exit with status 10 and message:
-        
+
 	status:
 	  ubuntu-core:
 	    error: Unknown config option "tea-in-the-morning"
 
 [snappy fails the install of the app]
-
-