Skip to content

Restructure comments.md with suggested format (#79) #277

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

Merged
merged 4 commits into from
Jun 27, 2025

Conversation

SamBSalgado
Copy link
Contributor

This pull request addresses issue #79 by restructuring the comments.md file in the English content directory.

Changes made:

  • Applied the section layout suggested in the issue:
    • Added ## Types of Comments with ### Single Line and ### Multi Line subsections.
    • Added a new section: ## Real life examples of comments with sample DOM manipulation code.
  • Improved paragraph structure for better readability.
  • Preserved original explanations and examples while enhancing clarity and formatting.

Let me know if any adjustments are needed. Happy to iterate!
Closes #79

Copy link

vercel bot commented Jun 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
learn-javascript ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 7:35pm

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR restructures the comments.md guide by introducing a clearer section layout and adding practical usage examples to improve readability.

  • Added a Types of Comments section with distinct Single-line and Multi-line subsections
  • Inserted a new Real-life Examples of Comments section showcasing DOM manipulation and debugging scenarios
  • Refined paragraph breaks and formatting for better flow and clarity
Comments suppressed due to low confidence (3)

en/basics/comments.md:13

  • [nitpick] Heading style is inconsistent: use hyphens in both section titles. Change ### Single Line Comments to ### Single-line Comments to match ### Multi-line Comments.
### Single Line Comments

en/basics/comments.md:11

  • [nitpick] After this heading, consider adding a brief introductory sentence (e.g., "In JavaScript, comments can be written in two ways: single-line and multi-line.") to guide readers into the subsections.
## Types of Comments

en/basics/comments.md:49

  • [nitpick] The two adjacent code fences for the disabled welcome message could be merged into one block to keep the explanatory comment and the commented-out code together, improving readability.
```javascript

Copy link
Owner

@sumn2u sumn2u left a comment

Choose a reason for hiding this comment

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

Nice work.

@sumn2u
Copy link
Owner

sumn2u commented Jun 27, 2025

Closes #79

@sumn2u sumn2u merged commit 2fef84d into sumn2u:main Jun 27, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Modify Comments section
2 participants