Skip to content

Fix improper idiom usage #5883

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 2 commits into from
Apr 6, 2023
Merged

Conversation

seriouscatsoserious
Copy link
Contributor

@seriouscatsoserious seriouscatsoserious commented Apr 5, 2023

The phrase "most of the times" is incorrect and would only make sense
in the context of a larger sentence. The phrase is actually "most of the
time" and is used in place of "usually".

There's 5 instances in this document in which the casing of a file name
begins with lower case, which makes it inconsisnent both with the page
and the entire tutorial.
The phrase "most of the times" is incorrect and would only make sense
in the context of a larger sentence. The phrase is actually "most of the
time" and is used in place of "usually".

When you write a _default_ import, you can put any name you want after `import`. For example, you could write `import Banana from './button.js'` instead and it would still provide you with the same default export. In contrast, with named imports, the name has to match on both sides. That's why they are called _named_ imports!
When you write a _default_ import, you can put any name you want after `import`. For example, you could write `import Banana from './Button.js'` instead and it would still provide you with the same default export. In contrast, with named imports, the name has to match on both sides. That's why they are called _named_ imports!
Copy link
Collaborator

@harish-sethuraman harish-sethuraman Apr 6, 2023

Choose a reason for hiding this comment

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

These changes were merged in this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@harish-sethuraman I'm very new to using Github, could you explain to me why it was that I pushed that old commit? Or direct to me a resource that explains? I did the same process for the second of the two commits, ie made sure everything was up to date from main branch, but for some reason the same one went through twice.

Copy link
Member

Choose a reason for hiding this comment

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

you probably created the second branch from your first branch rather than from main. so it included your last commit.

@gaearon gaearon merged commit d58ca81 into reactjs:main Apr 6, 2023
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.

4 participants