fix awkward split-phrase construction

to avoid that decryption for editing with ... too many clauses in a row

Signed-off-by: Kingdon Barrett <[email protected]>

content/en/flux/guides/helmreleases.md

@@ -505,8 +505,8 @@ this would work regardless but we may want to conventionally keep `values.yaml`
 in a file with the same name; then this rule may be a useful addition as well.
 
 The filename was also chosen to **not** match with `*.enc` or `*.encrypted` so
-that `sops` CLI never infers a binary input type, to avoid that decryption for
-editing with `sops my-values.enc.yaml` would also fail.
+that `sops` CLI never infers a binary input type, to avoid that decryption with
+`sops my-values.enc.yaml` for editing in-place would also fail.
 
 Be careful not to mix secrets with other non-sensitive data. A note that Helm
 stores its values as Kubernetes Secrets internally; if users can read secrets