docs(tutorial/step_03): improve explanation of camel-/kebab-casing

Related to #15051.

docs/content/guide/directive.ngdoc

@@ -70,7 +70,7 @@ Angular **normalizes** an element's tag and attribute name to determine which el
 directives. We typically refer to directives by their case-sensitive
 [camelCase](http://en.wikipedia.org/wiki/CamelCase) **normalized** name (e.g. `ngModel`).
 However, since HTML is case-insensitive, we refer to directives in the DOM by lower-case
-forms, typically using [dash-delimited](http://en.wikipedia.org/wiki/Letter_case#Computers)
+forms, typically using [dash-delimited](https://en.wikipedia.org/wiki/Letter_case#Special_case_styles)
 attributes on DOM elements (e.g. `ng-model`).
 
 The **normalization** process is as follows:

docs/content/tutorial/step_03.ngdoc

@@ -68,8 +68,9 @@ To create a component, we use the {@link angular.Module#component .component()}
 {@link module Angular module}. We must provide the name of the component and the Component
 Definition Object (CDO for short).
 
-Remember that (since components are also directives) the name of the component is in `camelCase`,
-but we will use `kebab-case`, when referring to it in our HTML.
+Remember that (since components are also directives) the name of the component is in `camelCase`
+(e.g. `myAwesomeComponent`), but we will use `kebab-case` (e.g. `my-awesome-component`) when
+referring to it in our HTML. (See [here][case-styles] for a description of different case styles.)
 
 In its simplest form, the CDO will just contain a template and a controller. (We can actually omit
 the controller and Angular will create a dummy controller for us. This is useful for simple
@@ -276,6 +277,7 @@ files, so it remains easy to locate as our application grows.
 <ul doc-tutorial-nav="3"></ul>
 
 
+[case-styles]: https://en.wikipedia.org/wiki/Letter_case#Special_case_styles
 [jasmine-docs]: http://jasmine.github.io/2.4/introduction.html
 [jasmine-home]: http://jasmine.github.io/
 [karma]: https://karma-runner.github.io/