turn on travis for preformat balance

Signed-off-by: Jess Frazelle <acidburn@google.com>

docs/user-guide/pods/init-container.md

@@ -20,7 +20,7 @@ the next one is started. If the init container fails, Kubernetes will restart
 the pod until the init container succeeds. If a pod is marked as `RestartNever`,
 the pod will fail if the init container fails.
 
-You specify a container as an init container by adding an annotation. 
+You specify a container as an init container by adding an annotation.
 The annotation key is `pod.beta.kubernetes.io/init-containers`.  The annotation
 value is a JSON array of [objects of type `v1.Container`
 ](http://kubernetes.io/docs/api-reference/v1/definitions/#_v1_container)
@@ -62,7 +62,7 @@ not able to access.
 
 Since init containers run to completion before any app containers start, and
 since app containers run in parallel, they provide an easier way to block or
-delay the startup of application containers until some precondition is met. 
+delay the startup of application containers until some precondition is met.
 
 Because init containers run in sequence and there can be multiple init containers,
 they can be composed easily.
@@ -77,7 +77,6 @@ Here are some ideas for how to use init containers:
 - Clone a git repository into a volume
 - Place values like a POD_IP into a configuration file, and run a template tool (e.g. jinja)
   to generate a configuration file to be consumed by the main app contianer.
-```
 
 Complete usage examples can be found in the [StatefulSets
 documentation](/docs/concepts/abstractions/controllers/statefulsets/) and the [Production Pods