Skip to content

Conversation

@anjalii-28
Copy link

This PR improves documentation readability by adding or correcting language
specifiers for fenced code blocks.

Changes are mechanical and limited to:

  • Adding missing language specifiers
  • Normalizing existing specifiers (bash, yaml, go, text)
  • No changes to documentation content or semantics

Directories touched:

  • docs/versioned/
  • docs/blog/articles/
  • code-samples/

Fixes #6526

@netlify
Copy link

netlify bot commented Jan 13, 2026

Deploy Preview for knative failed.

Built without sensitive environment variables

Name Link
🔨 Latest commit 990d8c5
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/69662a2dd4610f0008ad3778

@knative-prow
Copy link

knative-prow bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details Needs approval from an approver in each of these files:

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

@knative-prow knative-prow bot requested review from Leo6Leo, nainaz and pierDipi January 13, 2026 11:19
@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 13, 2026
@anjalii-28
Copy link
Author

Looks like the Netlify / Pages preview workflows are awaiting approval.
Could a maintainer please approve them when convenient?

@codeEvolveZenith345
Copy link
Contributor

codeEvolveZenith345 commented Jan 13, 2026

Hi @anjalii-28 The issue this PR addresses requires familiarity with the knative commands, It is not a good-first-issue.
And the overview of your submission demonstrates either you used Agent/AI or you do not know what those blocks exactly do.
In both the condition this PR requires major refactoring.

Hence revise it manually.

@anjalii-28
Copy link
Author

oh thanks, noted !

@anjalii-28 anjalii-28 closed this Jan 13, 2026
Copy link
Member

@Cali0707 Cali0707 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great cleanup @anjalii-28 !

I think it is worth re-opening this PR and then we can merge it in with the comments I left

I'm not sure if this has cleaned up all the code blocks in the docs folder (haven't had time to check if this gets all of them), but this is definitely an improvement

Now your scripts can access it via `localhost:8321`:

```shell
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I may make this one just text

We can now run our function locally by issuing `func run` on the command line. Once it is running there will a system log like below:

```shell
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one just text

You should have a webhook URL that looks like this:

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

You will see the output with the registry address:

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

You should see this message if the secret is created successfully:

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

```

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

You should see a service named `pipe` listed:

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text


Example output:
```shell
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text


Example output:
```shell
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

Example Output:

```sh
```bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this one text

@anjalii-28 anjalii-28 reopened this Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enhancement Proposal: Improve Code Block Language Specifiers Across Documentation

3 participants