Merge pull request #2948 from fluxcd/fix-links

Fix more links

CHANGELOG.md

@@ -941,8 +941,8 @@ Many thanks for contributions from @2opremio, @AndriiOmelianenko,
 [weaveworks/flux#2138]: https://github.com/weaveworks/flux/pull/2138
 [weaveworks/flux#2140]: https://github.com/weaveworks/flux/pull/2140
 [weaveworks/flux#2142]: https://github.com/weaveworks/flux/pull/2142
-[manifest-generation-docs]: https://github.com/weaveworks/flux/blob/master/site/fluxyaml-config-files.md
-[gpg-docs]: https://github.com/weaveworks/flux/blob/master/site/git-gpg.md
+[manifest-generation-docs]: https://github.com/fluxcd/flux/blob/master/docs/references/fluxyaml-config-files.md
+[gpg-docs]: https://github.com/fluxcd/flux/blob/master/docs/references/git-gpg.md
 
 ## 1.12.3 (2019-05-22)
 
@@ -1222,8 +1222,8 @@ syncs to fail when adding a CRD and instance(s) from that CRD at the same time.
 This release comes with experimental garbage collection and Git commit signing:
 
 1. Experimental garbage collection of cluster resources. When providing the
-   `--sync-garbage-collection` flag, cluster resources no longer existing in Git 
-   will be removed. Read the [garbage collection documentation](site/garbagecollection.md) 
+   `--sync-garbage-collection` flag, cluster resources no longer existing in Git
+   will be removed. Read the [garbage collection documentation](docs/references/garbagecollection.md)
    for further details.
 
 2. [GPG](https://en.wikipedia.org/wiki/GNU_Privacy_Guard)
@@ -1897,8 +1897,8 @@ reindent blocks the first time it changes a file.
 ### Experimental
 
 - Alpha release of
-  [helm-operator](https://github.com/weaveworks/flux/blob/master/site/helm/helm-integration.md). See
-  [./CHANGELOG-helmop.md](./CHANGELOG-helmop.md) for future releases.
+  [helm-operator](https://github.com/fluxcd/flux/blob/master/docs/references/helm-operator-integration.md). See
+  [./CHANGELOG-helmop.md](https://github.com/fluxcd/helm-operator/blob/master/CHANGELOG.md) for future releases.
 
 ## 1.2.3 (2018-02-07)
 

README.md

@@ -117,7 +117,7 @@ be interested in the following:
 
 - [Our contributions guidelines](CONTRIBUTING.md)
 - [Build documentation](https://docs.fluxcd.io/en/latest/contributing/building)
-- [Release documentation](/internal_docs/releasing.md)
+- [Release documentation](internal/docs/releasing.md)
 
 ## <a name="help"></a>Getting Help
 

docs/contributing/get-started-developing.md

@@ -227,7 +227,8 @@ and run what we have locally.
 ## Make some changes
 
 1. Now for the part you've been waiting for! We're going to make a
-   cosmetic change to our local copy of Flux. Navigate to [git/operations.go](https://github.com/fluxcd/flux/blob/master/git/operations.go).
+   cosmetic change to our local copy of Flux. Navigate to
+   [git/operations.go](https://github.com/fluxcd/flux/blob/master/pkg/git/operations.go).
    In it, you will find a private function to this package that goes
    by the name `execGitCmd`. Paste the following as the (new) first
    line of the function:

docs/references/daemon.md

@@ -107,4 +107,4 @@ Setting up and configuring `fluxd` is discussed in
 ["Get started with Flux"](../tutorials/get-started.md).
 
 There is also more information on [garbage collection](garbagecollection.md),
-[Git commit signing](git-gpg.md), and other elements in [references](./index).
+[Git commit signing](git-gpg.md), and other elements in [references](../).

docs/troubleshooting.md

@@ -62,7 +62,7 @@ to [this problem](https://github.com/fluxcd/flux/issues/1596). In
 short, there was a breaking change to how `kubectl` creates secrets,
 that found its way into the Kubernetes 1.13.0 release. It has been
 corrected in [kubectl
-v1.13.2](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md#changelog-since-v1131),
+v1.13.2](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.13.md#changelog-since-v1131),
 so using that version or newer to create secrets should fix the
 problem.
 

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 Docker Hub
- - possibly upload the [`fluxctl` binaries](/docs/references/fluxctl.md#binary-releases) to the GitHub release
+ - possibly upload the [`fluxctl` binaries](../../docs/references/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
  - close out the GitHub milestone that was used to track the release
 
@@ -60,7 +60,7 @@ The CircleCI script runs builds for tags, which push Docker images and upload bi
 5. Consider updating the deploy manifest examples and the Helm chart.
 
     The example manifests are generated from template manifests at
-    [pkg/install/templates](../pkg/install/templates), bump the Flux image tag
+    [pkg/install/templates](../../pkg/install/templates), bump the Flux image tag
     version and run `make generate-deploy`.
 
     Check the changes included in the release, to see if arguments, volume