docs(guide/directive): we are registering directives, not controllers

Closes #4615

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index b709b7e1..60b46357 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -168,7 +168,7 @@ For example, we could fix the example above by instead writing:
 ## Creating Directives
 
 First let's talk about the API for registering directives. Much like controllers, directives are registered on
-modules. To register a controller, you use the `module.directive` API. `module.directive` takes the
+modules. To register a directive, you use the `module.directive` API. `module.directive` takes the
 {@link guide/directive#creating-custom-directives_matching-directives normalized} directive name followed
 by a **factory function.** This factory function should return
 an object with the different options to tell `$compile` how the directive should behave when matched.