Fix typo in CSS code block under "Changes to the existing CSS"

Open Beginner friendly
#45,793 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
95/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
css, markdown
Domain
documentation

Research direction

Open files/en-us/learn_web_development/core/css_layout/practical_positioning_examples/index.md and find the "Changes to the existing CSS" section. Compare the prose with the code block, remove the outdated margin: 0 auto; line, and verify that the example matches the documented CSS changes.

Written by the indexing model from the issue text.

Description

Content:Learn:CSS good first issue
MDN URL

https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/CSS_layout/Practical_positioning_examples

What specific section or headline is this issue about?

#Changes to the existing CSS

What information was incorrect, unhelpful, or incomplete?

"Next we need to make some small changes to the existing CSS, to get the info-box placed and positioned. Change your .info-box rule to get rid of margin: 0 auto; (we no longer want the info-box centered), add position: fixed;, and stick it to the top of the browser viewport."

However, in the example code block right below this description, margin: 0 auto; was not removed:

What did you expect to see?

An example code block with the margin: 0 auto; rule removed:

.info-box {
width: 452px;
height: 400px;
position: fixed;
top: 0;
}

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata
Page report details
Dominant language
Markdown
Stars
11k
Forks
23.3k
Avg merge
1d 16h
Merged PRs (30d)
311

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 mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.