Skip to content

Unify custom resource spelling

Clemens Beck requested to merge docs-custom-resource-wording into master

What does this MR do?

Unify spelling of custom resource in all docs.

Before:

$ grep -r -oh -i "custom resource\|customresource" doc/ | sort | uniq -c
      9 custom resource
      5 Custom Resource
      5 CustomResource

Now:

$ grep -r -ho -i "custom resource\|customresource" doc/ | sort | uniq -c
     19 custom resource

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for omnibus-gitlab opened
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Related issues

Edited by Clemens Beck

Merge request reports