Remove how it works - updating readme

README.md

@@ -10,7 +10,7 @@ We like to think of it as `kubectl` for clusters.
 
 kops lets you deploy production grade (and HA) Kubernetes clusters in the cloud.
 
-We encourage everyone to read more about [how it works](/docs/how_it_works.md) or check out some of the [other interesting modes](/docs/commands.md#other-interesting-modes).
+We encourage everyone to read more about [adding a feature](/docs/adding_a_feature.md) before contributing.
 
 #### Quickstart
 

docs/adding_a_feature.md

@@ -61,6 +61,18 @@ so we leave the nil value as meaning "default policy, whatever it may be in futu
 So, we just need to check if `UpdatePolicy` is not nil and == `external`; we add the tag `_automatic_upgrades`,
 which enabled automatic upgrades, only if that is _not_ the case!
 
+## How it works
+
+Everything is driven by a local configuration directory tree, called the "model".  The model represents
+the desired state of the world.
+
+Each file in the tree describes a Task.
+
+On the nodeup side, Tasks can manage files, systemd services, packages etc.
+On the `kops update cluster` side, Tasks manage cloud resources: instances, networks, disks etc.
+
+
+
 ## Validation
 
 We should add some validation that the value entered is valid.  We only accept nil or `external` right now.

docs/how_it_works.md

@@ -1,10 +0,0 @@
-# How it works
-
-Everything is driven by a local configuration directory tree, called the "model".  The model represents
-the desired state of the world.
-
-Each file in the tree describes a Task.
-
-On the nodeup side, Tasks can manage files, systemd services, packages etc.
-On the `kops update cluster` side, Tasks manage cloud resources: instances, networks, disks etc.
-