feat: make the reference to create t3 app consistent

[Sboonny]

Closes #

✅ Checklist

• I have followed every step in the contributing guide (updated 2022-10-06).
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Changelog

Sometimes create-t3-app was wrapped in code elements, and sometimes it didn't. For consistency, I added the code elements around it, whenever it is in a description section.

---

Screenshots

in /en/folder-structure#tsconfigjson path

before

After

💯

[changeset-bot]

⚠️ No Changeset found

Latest commit: d644663

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Name	Status	Preview	Updated
create-t3-app	✅ Ready (Inspect)	Visit Preview	Jan 3, 2023 at 10:22AM (UTC)

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	80
🟢 Accessibility	100
🟢 Best practices	100
🟠 SEO	86
🟠 PWA	54

Lighthouse ran on https://create-t3-app-git-fork-sboonny-feat-wrap-code-ele-b82901-t3-oss.vercel.app/

[c-ehrlich]

I know this is currently done inconsistently in the docs, so maybe we can use this thread to discuss what makes sense. Here's some general thoughts:

• It should be "Create T3 App" or create-t3-app. Not "Create-T3-App" or anything else.
• I don't think either of the two is always the right version, so it makes sense to use both based on which feels better in any given paragraph
• There are probably some where currently the best choice isn't being used.

[Sboonny]

There are probably some where currently the best choice isn't being used.

🤔 Perhaps the links and the headings, too.

[Sboonny]

Oh btw, before I start changing stuff.

maybe we can use this thread to discuss what makes sense.

What about this, if create-t3-app refers to the CLI, we use create-t3-app. If it's refering to the stack, we use Create T3 App.

[juliusmarminge]

Oh btw, before I start changing stuff.

maybe we can use this thread to discuss what makes sense.

What about this, if create-t3-app refers to the CLI, we use create-t3-app. If it's refering to the stack, we use Create T3 App.

Makes sense to me.

[c-ehrlich]

Oh btw, before I start changing stuff.

maybe we can use this thread to discuss what makes sense.

What about this, if create-t3-app refers to the CLI, we use create-t3-app. If it's refering to the stack, we use Create T3 App.

I agree with this in general - the project itself is "Create T3 App", the cli/npm package is create-t3-app. I expect you'll find that there are some cases where it's difficult to separate the two, but if you want to go over the docs and give your opinions on this I think we'll end up with something that feels more consistent than what we have now :)

[Sboonny]

I will be honest, I was lazy and decided, if it "creates" or "sets up", then it's the CLI. 😄

I am open to suggestions.