Fix typos in composition functions documentation

[mergenci]

I corrected two typos in composition functions documentation. Because composition functions documentation doesn't exist in v1.11 and v1.12, there are no changes in those directories.

[netlify]

✅ Deploy Preview for crossplane ready!

Name	Link
🔨 Latest commit	a560ad1
🔍 Latest deploy log	https://app.netlify.com/sites/crossplane/deploys/651697d65bceab00086695e8
😎 Deploy Preview	https://deploy-preview-560--crossplane.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: Accessibility: Best Practices: SEO: PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[phisco]

@mergenci looks like Vale prefers "general-purpose": https://github.com/crossplane/docs/actions/runs/6349618710/job/17457649897?pr=560#step:5:261 😓

[mergenci]

@phisco did you mean Vale prefers “general purpose”, rather than “general-purpose”? Because, in the link you posted, I see a Crossplane.Spelling error for “general-purpose”.

How shall I address the error? Shall I define an exception for “general-purpose” in spelling-exceptions.txt? Or, do nothing, because “general-purpose” is valid usage?

By the way, I see more general problems in the Vale output:

1. “e.g.”, “i.e.”, and “general-purpose” are dictionary words that I can look up in my Mac's dictionary. Why are these not in Vale's, or Crossplane's, dictionary?
2. Vale, or Crossplane's configuration of Vale, doesn't seem to understand how hyphenation in English works. Vale reports errors for “build-time”, “in-place”, and “bug-fixes”. Even though I wouldn't prefer hyphenation in the latter two, they are certainly not spelling errors.

Is there anything that we can do to address the above issues?

[phisco]

Ah, I interpreted it the other way around, my bad, yes, it's complaining about the remaining occurrences of general-purpose. That's fine then, no need to go through all the errors, that section of the documentation will probably be reworked pretty intensively for the beta version with 1.14.

[plumbis]

Thanks for the update! I'm good with the Vale errors as we haven't gotten this page to pass Vale yet, so we can treat it as an exception for now.