Inconsistent case of "job" on k8s.io//docs/concepts/workloads/controllers/jobs-run-to-completion/ [File: /content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md]

[elizabethharris]

This is a...

• Feature Request
• Bug Report

Problem:
This page is inconsistent in its use of "Job" and "job". Which is correct? It looks like "Job" is used when the string is a literal (in code snippets, for example); but when it's not a literal, there's no apparent rhyme or reason to the upper/lower case usage.

Proposed Solution:
For non-literals, pick one and stick with it (probably lower-case "job"?). For literals, the content may be accurate.

Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/

Kubernetes Version: 1.11

[elizabethharris]

A similar issue found on https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/:
Cron Job
cron job
CronJob
Cronjob

The entry in the lefthand nav bar is "CronJob", so perhaps that's the spelling to go with?

BTW, this case/spelling issue is admittedly a nitpick, but users also need to know the right way to refer to these concepts (my current situation), so consistency in terms is actually really important :)

Thanks for fixing!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[elizabethharris]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.