Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed links to references of exact hooks. #178

Merged
merged 1 commit into from Sep 23, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/en/authors-hook-environment.md
Expand Up @@ -42,7 +42,7 @@ In addition, every relation hook makes available relation-specific variables.
important, because it's the only reasonable way of telling the difference
between (say) a database service's many independent clients.

...and, if that relation hook is not a [-broken](authors-charm-hooks.html#<name>-relation-broken) hook:
...and, if that relation hook is not a [-broken](authors-charm-hooks.html#[name]-relation-broken) hook:

- The `$JUJU_REMOTE_UNIT` variable holds the name of the unit which is
being reported to have -joined, -changed, or -departed.
Expand Down Expand Up @@ -276,7 +276,7 @@ necessarily _accurate_, in that you will always see settings that:

You should never depend upon the presence of any given key in `relation-get`
output. Processing that depends on specific values (other than `private-address`)
should be restricted to [-changed](authors-charm-hooks.html#<name>-relation-changed) hooks for the relevant unit, and the absence
should be restricted to [-changed](authors-charm-hooks.html#[name]-relation-changed) hooks for the relevant unit, and the absence
of a remote unit's value should never be treated as an
[error](./authors-hook-errors.html) in the local unit.

Expand Down