From a1806bb460403c5e6b8079fac7c3d604db139a55 Mon Sep 17 00:00:00 2001
From: Joey Organisak
Date: Wed, 23 Oct 2013 20:22:16 -0400
Subject: docs(guide/directive): we are registering directives, not controllers

Closes #4615
---
 docs/content/guide/directive.ngdoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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.
-- 
cgit v1.2.3