docs: keep the IPNS update example consistent

[dobshn]

Describe your changes

Update the “Make a change…” step to keep the tutorial consistent.

Explicitly use CIDv1 and publish /ipfs/ to reduce confusion from CIDv0 output and mixed /ipfs/ vs bare CID examples.

Docs-only change; Kubo accepts both forms.

Files changed

• docs/how-to/publish-ipns.md

What issue(s) does this address?

• N/A

Does this update depend on any other PRs?

• N/A

Checklist before requesting a review

• Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.

Checklist before merging

• Passing all required checks (The beta Check Markdown links for modified files check is not required)

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.
• Your contribution itself is clear (grammar and spelling checked, any code blocks checked and commented) and in its best form. Follow the docs contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.
• The PR gets reviews, discussed and approvals as needed.
• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[bumblefudge]

neat, thanks