docs(bike-shed-migration): fix url-based links refs to AUTO module

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/content/guide/dev_guide.services.creating_services.ngdoc b/docs/content/guide/dev_guide.services.creating_services.ngdoc
index c6210cc1..cdcd280b 100644
--- a/docs/content/guide/dev_guide.services.creating_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.creating_services.ngdoc
@@ -4,8 +4,8 @@
 
 While Angular offers several useful services, for any nontrivial application you'll find it useful
 to write your own custom services. To do this you begin by registering a service factory function
-with a module either via the {@link api/angular.module Module#factory api} or directly
-via the {@link api/AUTO.$provide $provide} api inside of module config function.
+with a module either via the {@link angular.module Module#factory api} or directly
+via the {@link auto.$provide $provide} api inside of module config function.
 
 All Angular services participate in {@link di dependency injection (DI)} by registering
 themselves with Angular's DI system (injector) under a `name` (id) as well as by declaring
@@ -17,8 +17,8 @@ testable.
 # Registering Services
 
 To register a service, you must have a module that this service will be part of. Afterwards, you
-can register the service with the module either via the {@link api/angular.Module Module api} or
-by using the {@link api/AUTO.$provide $provide} service in the module configuration
+can register the service with the module either via the {@link angular.Module Module api} or
+by using the {@link auto.$provide $provide} service in the module configuration
 function. The following pseudo-code shows both approaches:
 
 Using the angular.Module api:
@@ -103,4 +103,4 @@ important.
 
 ## Related API
 
-* {@link api/ng Angular Service API}
+* {@link ng Angular Service API}