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 some typography #1138

Closed
wants to merge 2 commits into from
Closed

Fix some typography #1138

wants to merge 2 commits into from

Conversation

Gauvino
Copy link
Contributor

@Gauvino Gauvino commented Sep 30, 2024

Hello, tried my best to fix all of the typography I could to have a clear documentation of Jellyfin.
I need some help on different change because I don't have the capacity to make the proper change for some things and will comment on every line I need help in.
I could make some error, so please be gentle and tell me why, thanks in advance.
This PR will probably make some conflict with most of the other PR is merged before, so feel free to merge it when you want!

@Gauvino Gauvino requested a review from a team as a code owner September 30, 2024 12:52
Copy link
Contributor Author

Choose a reason for hiding this comment

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

So, for these files I need the help of the whole jellyfin team to make a proper source tree, I tried my best for something but for the rest I don't really each project and maybe listing all of the other projects would be great !

@jellyfin-bot
Copy link

Cloudflare Pages deployment

Latest commit 6840cfdb3dc2acc36e79d71f83f31d08f733aeb9
Status ✅ Deployed!
Preview URL https://1704ca0d.jellyfin-org.pages.dev
Type 🔀 Preview

Copy link
Member

@felix920506 felix920506 left a comment

Choose a reason for hiding this comment

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

Reviewed everything clients and above
Please proof read the rest of the PR for similar cases that have been brought up.

docs/general/clients/kodi.md Show resolved Hide resolved
docs/general/clients/kodi.md Show resolved Hide resolved
docs/general/clients/kodi.md Show resolved Hide resolved
docs/general/clients/mopidy.md Show resolved Hide resolved
@@ -9,7 +9,7 @@ title: Jellyfin Web Configuration

The Jellyfin Web default interface can be configured using the `config.json` file in the webroot. Where this is and how to edit it depends on the installation method.

We recommend obtaining the [stable](https://github.com/jellyfin/jellyfin-web/blob/release-10.8.z/src/config.json) or the [unstable](https://github.com/jellyfin/jellyfin-web/blob/master/src/config.json) default version of the file to pre-populate your configuration directory before starting Jellyfin for the first time; unlike most other components of this directory, it will not be created automatically.
We recommend obtaining the [stable](https://github.com/jellyfin/jellyfin-web/blob/release-10.8.z/src/config.json) or the [unstable](https://github.com/jellyfin/jellyfin-web/blob/master/src/config.json) default version of the file to pre-populate your configuration directory before starting Jellyfin for the first time; Unlike most other components of this directory, it will not be created automatically.
Copy link
Member

Choose a reason for hiding this comment

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

you don't need to capitalize after semicolon

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do I need to make this on every semicolon I did change ?

@joshuaboniface
Copy link
Member

joshuaboniface commented Oct 1, 2024

First, this is a massive PR and I'm not in favour of a massive single change like this, for the reasons below.

Second, there's some changes in here that are good, and some that make no sense or are outright wrong. But because it's so large, commenting on each one would be a massive burden on us.

Third, it looks like you just ran the entire docs repo through a spellchecker. As a first step that's fine, but committing the results blindly is not good form.

Please split this into multiple smaller PRs targeting specific areas first, and ensure each one is well-proofread before submitting. We can then take each individual change individually for comment as required.

@Gauvino
Copy link
Contributor Author

Gauvino commented Oct 9, 2024

First, this is a massive PR and I'm not in favour of a massive single change like this, for the reasons below.

No problem I totally understand this point.

Second, there's some changes in here that are good, and some that make no sense or are outright wrong. But because it's so large, commenting on each one would be a massive burden on us.

Third, it looks like you just ran the entire docs repo through a spellchecker. As a first step that's fine, but committing the results blindly is not good form.

Yes I did use a spell check, and use my English also to make the best, but I'm not that good so I did my best.

Please split this into multiple smaller PRs targeting specific areas first, and ensure each one is well-proofread before submitting. We can then take each individual change individually for comment as required.

Right now I can't do this I don't have any time left, but when I got some I'll do everything I could, yes!

@Gauvino
Copy link
Contributor Author

Gauvino commented Oct 9, 2024

Reviewed everything clients and above Please proof read the rest of the PR for similar cases that have been brought up.

Thanks you for taking time to make a proper review on my PR !

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.

5 participants