diff --git a/docs/content/tutorial/step_07.ngdoc b/docs/content/tutorial/step_07.ngdoc
index 1e86b2565286..b7d635a88287 100644
--- a/docs/content/tutorial/step_07.ngdoc
+++ b/docs/content/tutorial/step_07.ngdoc
@@ -56,9 +56,9 @@ module definitions. The sole responsibilities of the injector are to load specif
 definition(s), register all service providers defined in these modules and when asked inject
 a specified function with dependencies (services) that it lazily instantiates via their providers.
 
-Providers are objects that provide (create) instances of services and expose configuration apis
+Providers are objects that provide (create) instances of services and expose configuration APIs
 that can be used to control the creation and runtime behavior of a service. In case of the `$route`
-service, the `$routeProvider` exposes apis that allow you to define routes for your application.
+service, the `$routeProvider` exposes APIs that allow you to define routes for your application.
 
 Angular modules solve the problem of removing global state from the application and provide a way
 of configuring the injector. As opposed to AMD or require.js modules, Angular modules don't try to
@@ -79,8 +79,8 @@ angular.module('phonecat', []).
 </pre>
 
 In order to configure our application with routes, we need to create a module for our application.
-We call this module `phonecatApp` and using the `config` api we request the `$routeProvider` to be
-injected into our config function and use `$routeProvider.when` api to define our routes.
+We call this module `phonecatApp` and using the `config` API we request the `$routeProvider` to be
+injected into our config function and use `$routeProvider.when` API to define our routes.
 
 Note that during the injector configuration phase, the providers can be injected as well, but they
 will not be available for injection once the injector is created and starts creating service