Fixed numbering for installation steps in the tip

[archups]

Please provide a description for what this PR is for.

And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.

• Ambient
• [ x] Docs
• Installation
• Networking
• Performance and Scalability
• Extensions and Telemetry
• Security
• Test and Release
• User Experience
• Developer Infrastructure

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: archups / name: Archana Sawant (1b7bd3d, b5ce076)

[istio-policy-bot]

😊 Welcome! This is either your first contribution to the Istio documentation repo, or
it's been awhile since you've been here. A few things you should know:

• You can learn about how we write and maintain documentation, about our style guidelines,
  and about all the available web site features by visiting Contributing to the Docs.

• In the next few minutes, an automatic preview of your change will be
  built as a full copy of the istio.io website. You can find this preview by clicking on
  the Details link next to the deploy/netlify entry in the Status section of this
  page.

• We care about quality, so we've put in place a number of checks to ensure our documentation
  is top notch. We do spell checking, we sanitize the markdown, we ensure all hyperlinks point
  to valid location, and more. If your PR doesn't pass one of these checks, you'll see a red X in the
  status section of the page. Click on the Details link to get a list of the problems with your PR.
  Fix those problems and push an update to your PR. This will automatically rerun the tests and
  hopefully this time everything will be perfect.

• Once your changes are accepted and merged into the repository, they will initially show up
  on https://preliminary.istio.io. The changes will be published to https://istio.io
  the next time we do a major release (which typically happens every 3 months or so).

Thanks for contributing!

Courtesy of your friendly welcome wagon.

[istio-testing]

Hi @archups. Thanks for your PR.

I'm waiting for a istio 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/test-infra repository.

[ericvn]

The original numbers are correct. All items should be labeled 1., and the will be automatically numbered,

[Arhell]

/ok-to-test

[archups]

The original numbers are correct. All items should be labeled 1., and the will be automatically numbered,

@ericvn Yes, it works usually that way, but not within tip. Please check the rendered number on the doc site itself https://istio.io/latest/docs/setup/install/operator/.
Hence PR raised for fix. Thanks for review!

[ericvn]

If numbering doesn't work, I'd maybe recommend just using - instead of #. and just have bullets. @frankbu thoughts?

[frankbu]

Using 1) and 2) for the list items, instead of 1. and 2., might work.

[ericvn]

Using 1) and 2) for the list items, instead of 1. and 2., might work.

I did try that locally, and it didn't seem to work for me. Also tried some indentation changes.

[frankbu]

I did try that locally, and it didn't seem to work for me.

What did it display? It should work.

[ericvn]

I did try that locally, and it didn't seem to work for me.

What did it display? It should work.

Using 1. It showed both as 1. which is the problem to solve. Changing to 1) left them both showing as 1. Changing to - showed each as a bullet. All this with no other indentation. Looking at the public index.html with the )s:

<div>
    <aside class="callout tip">
        <div class="type">
            <svg class="large-icon"><use xlink:href="/img/icons.svg#callout-tip"/></svg>
        </div>
        <div class="content"><p>You can alternatively deploy the operator using Helm:</p>
<ol>
<li>
<p>Create a namespace <code>istio-operator</code>.</p>
 <pre><code class='language-bash' data-expandlinks='true' data-repo='istio' >$ kubectl create namespace istio-operator
</li>
</ol>
<p></code></pre></p>
<ol>
<li>
<p>Install operator using Helm.</p>
 <pre><code class='language-bash' data-expandlinks='true' data-repo='istio' >$ helm install istio-operator manifests/charts/istio-operator \
 --set watchedNamespaces=&#34;istio-namespace1\,istio-namespace2&#34; \
 -n istio-operator
</li>
</ol>
<p></code></pre></p>
<p>Note that you need to <a href="/docs/setup/getting-started/#download">download the Istio release</a>
to run the above command.</p>
</div>
    </aside>
</div>

[ericvn]

Looking through other parts of the doc, I do see #) used, most notably it seems when we need to restart numbering at some number. And it seems to be around tabsets. I really didn't see anything that related to numbering within a tip, and only see 2. used within a section header.

Looking at this particular page, I don't really see numbering used at all, except in this tip, so removing the numbering makes sense to me. Keeping a bullet (using -) does seem like an acceptable change if we wanted to call out the steps separately.

[frankbu]

Looking through other parts of the doc, I do see #) used, most notably it seems when we need to restart numbering at some number.

Markdown lets you continue a list that otherwise is disconnected from the previous items by specifying something other than 1 for the entry, but the lint rule we've enabled for the docs (MD029) requires all list entries to be 1, so it won't allow 2.. The work around is that the lint rule only enforces the rule for the . syntax, but markdown allows either . or ) for ordered lists. So using 2) won't cause a lint error, and will continue the list at 2. Here's what I get when I tried:

[frankbu]

Suggested change

	2. Install operator using Helm.
	2) Install operator using Helm.

[frankbu]

Suggested change

	2. 使用 Helm 安装 Operator。
	2) 使用 Helm 安装 Operator。

dismiss obsolete review

[ericvn]

/cherry-pick release-1.19

[istio-testing]

@ericvn: new pull request created: #13850

In response to this:

/cherry-pick release-1.19

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.