adds links to fluxctl from other files

internal_docs/releasing.md

@@ -4,7 +4,7 @@ The release process needs to do these things:
 
  - create a new release on GitHub, with a tag
  - push Docker image(s) to quay.io
- - possibly upload the `fluxctl` binaries to the GitHub release
+ - possibly upload the [`fluxctl` binaries](/site/fluxctl.md#binary-releases) to the GitHub release
  - make sure the version is entered into the checkpoint database so
    that up-to-date checks report back accurate information
 

site/annotations-tutorial.md

@@ -93,7 +93,7 @@ weaveworks/flux
 
 > **Note:** In this tutorial we keep things simple, so we deploy Flux into
 the `default` namespace. Normally you would pick a separate namespace for
-it. `fluxctl` has the `--k8s-fwd-ns <NAMESPACE>` option for specifying the right
+it. `fluxctl` has the [`--k8s-fwd-ns <NAMESPACE>` option](fluxctl.md#Connectingfluxctltothedaemon) for specifying the right
 namespace.
 
 ### Connecting to your git config

site/faq.md

@@ -135,7 +135,9 @@ applying the command. This is done to ensure that git remains the single source
 
 For example, if you use the following `fluxctl` command:
 
-    fluxctl release --controller=deployment/foo --update-image=bar:v2
+```sh
+fluxctl release --controller=deployment/foo --update-image=bar:v2
+```
 
 The image tag will be updated in the git repository upon applying the command.
 

site/how-it-works.md

@@ -23,7 +23,7 @@ with an orchestrator (which is a common source of accidental failure) or
 with the systems that ensure that the orchestrator is in a working
 state.
 
-Flux provides a CLI (`fluxctl`) and a UI (as a component of Weave Cloud)
+Flux provides a CLI ([`fluxctl`](fluxctl.md)) and a UI (as a component of Weave Cloud)
 to perform these operations manually. Flux is flexible enough to fit
 into any development process.