From 3b1c76a1dae2e8da2d26983dbb1a57bf1324f958 Mon Sep 17 00:00:00 2001 From: Peter Robins Date: Thu, 2 Jun 2016 15:29:41 +0100 Subject: [PATCH] Correct typo in config/jsdoc/api/readme.md --- config/jsdoc/api/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/jsdoc/api/readme.md b/config/jsdoc/api/readme.md index a7e34c7763..3e9fc21b09 100644 --- a/config/jsdoc/api/readme.md +++ b/config/jsdoc/api/readme.md @@ -24,7 +24,7 @@ The second line tells the Closure compiler the type of the argument. The third line (`@api`) marks the method as part of the api and thus exportable. The stability can be added as value, e.g. `@api stable`. Without such an api annotation, the method will not be documented in the generated API documentation. Symbols without an api annotation will also not be exportable (unless they are explicitly exported with a `goog.exportProperty` call). -The `@api` annotation can be used in conjunciton with the `@inheritDoc` annotation to export a symbol that is documented on a parent class (where the method may be abstract). In general, `@api` annotations should never be used on abstract methods (only on their implementations). +The `@api` annotation can be used in conjunction with the `@inheritDoc` annotation to export a symbol that is documented on a parent class (where the method may be abstract). In general, `@api` annotations should never be used on abstract methods (only on their implementations). ### Events