Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos, literal translations and grammatical errors in Korean documents #1267

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

hwahyeon
Copy link
Contributor

@hwahyeon hwahyeon commented Feb 9, 2024

Description

Fixed typos, wrong translations and grammatical errors in Korean dacuments (1-getting-started-lessons)

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

@hwahyeon
Copy link
Contributor Author

hwahyeon commented Feb 9, 2024

@microsoft-github-policy-service agree

@chandan-kumar-sagar
Copy link

Fixed typos, wrong translations and grammatical errors in Korean dacuments (1-getting-started-lessons)

Fixes # (issue)

Type of change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

@chandan-kumar-sagar
Copy link

@microsoft-github-policy-service agree

@hwahyeon hwahyeon changed the title Fix typos, literal translations and grammatical errors in Korean dacuments Fix typos, literal translations and grammatical errors in Korean documents Feb 9, 2024
@hwahyeon
Copy link
Contributor Author

hwahyeon commented Feb 9, 2024

@chandan-kumar-sagar Hi, I noticed you've copied and pasted the content of my PR into a comment. Is there a specific point you were looking to highlight or any additional clarifications needed on this section? I'd appreciate it if you could share them in detail. Thanks.

Copy link

This PR has not seen any action for a while! Closing for now, but it can be reopened at a later date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants