Doc typos

docs/controllers.md

@@ -153,7 +153,7 @@ If the `Client` table is omitted from the service, the service will be interpret
 
 ## KnitInit and KnitStart
 
-The `KnitInit` and `KnitStart` methods are optional lifecycle methods that can be added to any controller. For more info, check out the [service version](services.md#knitinit-and-knitstart) of this section (which has the same behavior) and the [execution model](executionmodel.md).
+The `KnitInit` and `KnitStart` methods are optional lifecycle methods that can be added to any controller. For more info, check out [Services: KnitInit and KnitStart](services.md#knitinit-and-knitstart) (which has the same behavior) and the [execution model](executionmodel.md).
 
 These methods can be added just like any other method:
 

docs/services.md

@@ -169,7 +169,7 @@ end)
 
 ### Signals (Server-to-Client)
 
-We should also create a signal that we can fire events for the clients when their points change. We can use `Knit:CreateSignal()` to indicate we want a signal created for the service.
+We should also create a signal that we can fire events for the clients when their points change. We can use `Knit.CreateSignal()` to indicate we want a signal created for the service.
 
 ```lua
 local PointsService = Knit.CreateService {