docs: fix md code syntax to prevent issues on documentation rendering

[serut]

It's hard to read the document right now as the code syntax without any type (yaml, shell, text) does not have any default rendering

I've made the requested changes on several pages to just make it work for now

[linux-foundation-easycla]

• ✅ login: serut / name: lmieulet (42d5f36, ad9633c, 5eb7853, 4b2a2f2, a1572f8, d3d9b16, cd0417e, dead5d6, 6b9ce91, fd62a21, 3f6c2b4, 4d22947)
• ❌ The email address for the commit (92b412b, 052b231) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serut
Once this PR has been reviewed and has the lgtm label, please assign medyagh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @serut!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @serut. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[minikube-bot]

Can one of the admins verify this patch?

[medyagh]

same comment for other blocks

[medyagh]

this is not quite shell, this is minikube output, would that make it look better?

[serut]

if it gets out from a terminal, it's out from shell no ?
There is no coloration on shell most of the time with such output so it does not matter

[serut]

I'm coming back to this MR to see if I can help you with the review

With "shell" coloration :

With "text" coloration :

Without this MR :

[serut]

I think text is better, as sometimes the color is pointless. Here is an example:

Text:

Shell:

[serut]

Ok there is no more problem of code syntax rendering with the last version of the documentation.
it's related to the upgrade of hugo from v0.146.6 to v0.147.1 #20700

MR #20681 can be closed too