Typo on page

Open Beginner friendly
#38,063 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
docker
Domain
documentation

Research direction

Open docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md and find the paragraph describing Docker's EXPOSE setting. Correct the displayed TPC typo to TCP, then check the zh-cn page and the source diff to confirm the error paragraph is fixed without changing its meaning.

Written by the indexing model from the issue text.

Description

dotnet-architecture/svc good first issue help wanted microservices/subsvc okr-quality
Type of issue

Typo

Description

Website:

This was raised in https://developercommunity.visualstudio.com/t/Microsoft-learn-text-error-TCP---TPC/10513633 so creating the issue here. Looks like this doesn't reproduce on en-us but does on zh-cn, unsure on other languages

Error paragraph:

you also need to instruct Docker to listen on the TCP port to be used at runtime (the TPC port configured by the EXPOSE setting in the example is 80).

Page URL

https://learn.microsoft.com/zh-cn/dotnet/architecture/microservices/docker-application-development-process/docker-app-development-workflow?source=recommendations

Content source URL

https://github.com/dotnet/docs/blob/main/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md

Document Version Independent Id

c8fefbe8-6f9b-209a-3563-2cb51384707c

Article author

jamesmontemagno

Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
15h 30m
Merged PRs (30d)
374

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/docs

All issues in dotnet/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.