diff --git a/docs/getting-started-guides/rkt/index.md b/docs/getting-started-guides/rkt/index.md
index 47a9a66077..e644b52462 100644
--- a/docs/getting-started-guides/rkt/index.md
+++ b/docs/getting-started-guides/rkt/index.md
@@ -22,8 +22,8 @@ must be running on the node.
 
 rkt uses the [Container Network Interface (CNI)](https://github.com/appc/cni)
 to manage container networking. By default, all pods attempt to join a network
-called `rkt.kubernetes.io`, which is currently defined [in `rkt.go`]
-(https://github.com/kubernetes/kubernetes/blob/v1.2.0-alpha.6/pkg/kubelet/rkt/rkt.go#L91).
+called `rkt.kubernetes.io`, which is currently defined [in
+`rkt.go`](https://github.com/kubernetes/kubernetes/blob/v1.2.0-alpha.6/pkg/kubelet/rkt/rkt.go#L91).
 In order for pods to get correct IP addresses, the CNI config file must be
 edited to add this `rkt.kubernetes.io` network:
 
@@ -216,4 +216,4 @@ where `$UUID` is the rkt pod's UUID, which you can find via `rkt list --full`, a
 
 ##### Check Kubernetes events, logs.
 
-Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/docs/user-guide/application-troubleshooting)
\ No newline at end of file
+Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/docs/user-guide/application-troubleshooting)