Merge lp:~evilnick/juju-core/docs-apparmor-bug1188681 into lp:juju-core/docs

[Nick Veitch]

added link for apparmor

=== modified file 'htmldocs/authors-charm-policy.html'
--- htmldocs/authors-charm-policy.html	2013-12-06 09:48:59 +0000
+++ htmldocs/authors-charm-policy.html	2013-12-13 15:25:45 +0000
@@ -88,7 +88,7 @@
                 <li>Must not run any network services using default passwords.</li>
                 <li>Must call Juju API tools (relation-*, unit-*, config-*, etc) without a hard coded path. Should default to use software that is included in the Ubuntu archive, however we encourage that charm authors have a config options for allowing users to deploy from newer upstream releases, or even right from VCS if it's useful to users.</li>
                 <li>Should not use anything infrastructure-provider specific (i.e. querying EC2 metadata service) symlinks must be self contained within a charm.</li>
-                <li>Should make use of AppArmor to increase security.</li>
+                <li>Should make use of <a href="https://help.ubuntu.com/12.04/serverguide/apparmor.html">AppArmor</a> to increase security.</li>
                 <li>Bundles must only use charms which are already in the store, they cannot reference charms in personal namespaces.</li>
                 </ul>
                 <p>The charm store referred to in this document is the collection of Juju charms and bundles hosted at <a href="https://launchpad.net/charms">https://launchpad.net/charms</a>.</p>