Merge pull request #804 from ljdelight/bookLinks

📖 replace some todo links to the documentation

Author: k8s-ci-robot

docs/book/src/cronjob-tutorial/controller-overview.md

@@ -11,7 +11,7 @@ matches the desired state in the object.  Each controller focuses on one
 We call this process *reconciling*.
 
 In controller-runtime, the logic that implements the reconciling for
-a specific kind is called a [*Reconciler*](../TODO.md).  A reconciler
+a specific kind is called a [*Reconciler*](https://godoc.org/sigs.k8s.io/controller-runtime/pkg/reconcile).  A reconciler
 takes the name of an object, and returns whether or not we need to try
 again (e.g. in case of errors or periodic controllers, like the
 HorizontalPodAutoscaler).

docs/book/src/cronjob-tutorial/testdata/emptyapi.go

@@ -61,10 +61,10 @@ In general, we never modify either of these -- all modifications go in either Sp
 
 That little `+kubebuilder:object:root` comment is called a marker.  We'll see
 more of them in a bit, but know that they act as extra metadata, telling
-[controller-tools](../TODO.md) (our code and YAML generator) extra information.
+[controller-tools](https://github.com/kubernetes-sigs/controller-tools) (our code and YAML generator) extra information.
 This particular one tells the `object` generator that this type represents
 a Kind.  Then, the `object` generator generates an implementation of the
-[`runtime.Object`](../TODO.md) interface for us, which is the standard
+[runtime.Object](https://godoc.org/k8s.io/apimachinery/pkg/runtime#Object) interface for us, which is the standard
 interface that all types representing Kinds must implement.
 */
 
@@ -90,7 +90,7 @@ type CronJobList struct {
 
 /*
 Finally, we add the Go types to the API group.  This allows us to add the
-types in this API group to any [scheme](../TODO.md).
+types in this API group to any [Scheme](https://godoc.org/k8s.io/apimachinery/pkg/runtime#Scheme).
 */
 func init() {
 	SchemeBuilder.Register(&CronJob{}, &CronJobList{})

docs/book/src/cronjob-tutorial/testdata/emptycontroller.go

@@ -54,10 +54,10 @@ need to revisit these.
 
 /*
 `Reconcile` actually performs the reconciling for a single named object.
-Our [`Request`](../TODO.md) just has a name, but we can use the client to fetch
+Our [Request](https://godoc.org/sigs.k8s.io/controller-runtime/pkg/reconcile#Request) just has a name, but we can use the client to fetch
 that object from the cache.
 
-We return a empty result and no error, which indicates to controller-runtime that
+We return an empty result and no error, which indicates to controller-runtime that
 we've succesfully reconciled this object and don't need to try again until there's
 some changes.
 

docs/book/src/cronjob-tutorial/testdata/project/api/v1/cronjob_types.go

@@ -34,14 +34,14 @@ First, let's take a look at our spec.  As we discussed before, spec holds
 Fundamentally a CronJob needs the following pieces:
 
 - A schedule (the *cron* in CronJob)
-- A template to for the Job to run (the
+- A template for the Job to run (the
 *job* in CronJob)
 
 We'll also want a few extras, which will make our users' lives easier:
 
 - A deadline for starting jobs (if we miss this deadline, we'll just wait till
   the next scheduled time)
-- What do to if multiple jobs would run at once (do we wait? stop the old one? run both?)
+- What to do if multiple jobs would run at once (do we wait? stop the old one? run both?)
 - A way to pause the running of a CronJob, in case something's wrong with it
 - Limits on old job history
 
@@ -50,7 +50,7 @@ keep track of whether a job has run.  We can use at least one old job to do
 this.
 
 We'll use several markers (`// +comment`) to specify additional metadata.  These
-will be used by [controller-tools](../TODO.md) when generating our CRD manifest.
+will be used by [controller-tools](https://github.com/kubernetes-sigs/controller-tools) when generating our CRD manifest.
 As we'll see in a bit, controller-tools will also use GoDoc to form descriptions for
 the fields.
 */