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

docs: better grammar and spelling #187

Merged
merged 2 commits into from
Nov 22, 2024
Merged

docs: better grammar and spelling #187

merged 2 commits into from
Nov 22, 2024

Conversation

LumiFae
Copy link

@LumiFae LumiFae commented Nov 20, 2024

Description

Here all I do is change some minor things like the documentation where the English used is incorrect or just has spelling mistakes.

What is the current behavior? (You can also link to an open issue here)
No behaviour

What is the new behavior? (if this is a feature change)
No behaviour

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:


Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentations

Submission checklist

  • I have checked the project can be compiled
  • I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

  • I have checked no IL patching errors in the console

Other

  • Still requires more testing

"Whether or not" is incorrect, even though it is understandable, the language is incorrect and can just be whether, as whether infers there is a negative and a positive, https://english.stackexchange.com/questions/3382/whether-or-not-vs-whether. In the case of this, "or not" in "Whether or not" is not needed, as it is always undetermined the response in the documentation, the documentation won't know.
Can remove the "or not" when there is a whether in there
Copy link
Member

@VladTheCow VladTheCow left a comment

Choose a reason for hiding this comment

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

I'd say the changes are useless

@LumiFae
Copy link
Author

LumiFae commented Nov 20, 2024

Maybe, maybe not, but it's correct English and if it's not wanted then fine, I just thought I would help out. I have some more changes I want to make too but not like this, just general documentation changes where clarification is needed

@Misaka-ZeroTwo
Copy link
Collaborator

I always thought Stylecop made it whether or not.

@LumiFae
Copy link
Author

LumiFae commented Nov 21, 2024

I would hope not, but I got no stylecop related errors so

Copy link

@VALERA771 VALERA771 left a comment

Choose a reason for hiding this comment

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

This is the biggest breaking changes I've ever seen! (joke)

@VALERA771
Copy link

Can you try compiling project on release? If you have already done it then put a tick in description

@Misaka-ZeroTwo
Copy link
Collaborator

Can you try compiling project on release? If you have already done it then put a tick in description

Dev CI builds in release mode

@louis1706
Copy link

I always thought Stylecop made it whether or not.

I honestly thought the same so that weird i would have expected error.

@VALERA771 VALERA771 mentioned this pull request Nov 22, 2024
8 tasks
@LumiFae
Copy link
Author

LumiFae commented Nov 22, 2024

Can you try compiling project on release? If you have already done it then put a tick in description

Let me try now

@LumiFae
Copy link
Author

LumiFae commented Nov 22, 2024

Only error I get is

3>Microsoft.Common.CurrentVersion.targets(5932,5): Error MSB3073 : The command "if not "C:\Users\Jay\Documents\GitHub\EXILED\EXILED\bin\Debug"=="" copy /y "C:\Users\Jay\Documents\GitHub\EXILED\EXILED\\bin\Debug\Exiled.Permissions.dll" "C:\Users\Jay\Documents\GitHub\EXILED\EXILED\bin\Debug\Plugins\"" exited with code 1.
3>------- Finished building project: Exiled.Permissions. Succeeded: False. Errors: 1. Warnings: 0

I don't think it has any relevance though, everything else passed

Copy link

@Jesus-QC Jesus-QC left a comment

Choose a reason for hiding this comment

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

Lgtm

@Jesus-QC Jesus-QC merged commit 78cd561 into ExMod-Team:dev Nov 22, 2024
5 checks passed
@Jesus-QC
Copy link

I always thought Stylecop made it whether or not.

I think they changed it recently and decided to remove the or not part.

Copy link

@Mikihero Mikihero left a comment

Choose a reason for hiding this comment

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

ultimately doesn't matter but there is no reason to not merge it imo

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.

7 participants