Apply suggestions from code review

Co-Authored-By: stefanprodan <stefan.prodan@gmail.com>
fluxcd · Nov 19, 2018 · e25f014 · e25f014
1 parent 82569d8
commit e25f014
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/chart/flux/README.md b/chart/flux/README.md
@@ -27,8 +27,8 @@ until it can find one.
 
 # Git repo
 
- - One repo containing desired release state information and Charts themselves.
- - Charts are co-located under another path or can be referenced from Helm repositories.
+ - One repo containing cluster config (i.e., Kubernetes YAMLs) and zero or more git repos containing Charts themselves.
+ - Charts can be co-located with config in the git repo, or be from Helm repositories.
  - Custom Resource namespace reflects where the release should be done.
    Both the Helm release and its corresponding Custom Resource will
    live in this namespace.

diff --git a/site/faq.md b/site/faq.md
@@ -418,7 +418,7 @@ You need to use the `helm delete --purge` option only then Flux will be able rei
 
 ### I've uninstalled Flux and all my Helm releases are gone. Why is that?
 
-On `FluxHelmRelease` CRD deletion, Kubernetes will remove all `HelmRelease` CRs triggering a Helm purge for each release created by Flux.
+On `HelmRelease` CRD deletion, Kubernetes will remove all `HelmRelease` resources triggering a Helm purge for each release created by Flux.
 To avoid this you have to manually delete the Flux Helm Operator with `kubectl -n flux delete deployment/flux-helm-operator` before running `helm delete flux`.
 
 ### I have a dedicated Kubernetes cluster per environment and I want to use the same Git repo for all. How can I do that?