Merge lp:~adam-collard/juju-core/implicit-relations-typo into lp:juju-core/docs

[Adam Collard]

Fix small typo in Implicit Relations page and a tiny whitespace issue.

[Nick Veitch (evilnick)]

Ta. I also noticed the use of Juju, which we (should) use caps for when not talking about the command.

[Adam Collard (adam-collard)]

> Ta. I also noticed the use of Juju, which we (should) use caps for when not
> talking about the command.

Do you want me to include fixes to that in this branch?

[Nick Veitch (evilnick)]

If you can, that would be cool, then I will merge. Thanks for looking all this over, it really is a help!

[Adam Collard (adam-collard)]

> If you can, that would be cool, then I will merge. Thanks for looking all this
> over, it really is a help!

Done! No problem, glad I can help :)

=== modified file 'htmldocs/authors-implicit-relations.html'
--- htmldocs/authors-implicit-relations.html	2013-09-27 14:53:30 +0000
+++ htmldocs/authors-implicit-relations.html	2013-10-05 11:32:36 +0000
@@ -67,10 +67,10 @@
         <div class="grid-9 doc-content">
 <!--End-Preamble-->
           <article>
-            <section id ="implicit-relations">
+            <section id="implicit-relations">
             <h1>Implicit relations</h1>
             <p>Implicit relations allow for interested services to gather lifecycle-oriented events and data about other services without expecting or requiring any modifications on the part of the author of the other service's charm.</p>
-            <p>Implicit relationships are named in the reserved the juju-* namespace. Both the relation name and interface names provided by juju are prefixed with <cite>juju-</cite>. Charms attempting to provide new relationships in this namespace will trigger an error.</p>
+            <p>Implicit relationships are named in the reserved juju-* namespace. Both the relation name and interface names provided by Juju are prefixed with <cite>juju-</cite>. Charms attempting to provide new relationships in this namespace will trigger an error.</p>
             <p>Juju currently provides one implicit relationship to all deployed services.</p>
             <p><cite>juju-info</cite>, if specified would look like:</p>
             <pre>provides:
@@ -95,7 +95,7 @@
             <p>The admin then issues the following</p>
             <pre>juju add-relation wordpress rsyslog</pre>
             
-            <p>If the wordpress charm author doesn't define the <cite>logging-directory</cite> interface juju will use the less-specific (in the sense that it likely provides less information) <cite>juju-info</cite> interface. juju always attempts to match user provided relations outside the <cite>juju-*</cite> namespace before looking for possible relationship matches in the <cite>juju-*</cite> namespace.</p>
+            <p>If the wordpress charm author doesn't define the <cite>logging-directory</cite> interface Juju will use the less-specific (in the sense that it likely provides less information) <cite>juju-info</cite> interface. Juju always attempts to match user provided relations outside the <cite>juju-*</cite> namespace before looking for possible relationship matches in the <cite>juju-*</cite> namespace.</p>
             
             </section>
           </article>