Skip to content

Conversation

@rolnico
Copy link
Member

@rolnico rolnico commented Sep 26, 2025

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?
No

What kind of change does this PR introduce?
Fixes

What is the current behavior?
Typos

What is the new behavior (if this is a feature change)?
Less typos

Does this PR introduce a breaking change or deprecate an API?

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

@rolnico rolnico requested a review from colineplqt September 26, 2025 06:17
@rolnico rolnico self-assigned this Sep 26, 2025
@rolnico rolnico requested a review from alicecaron September 26, 2025 06:18
Copy link
Member

@colineplqt colineplqt left a comment

Choose a reason for hiding this comment

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

A few suggestions but I am not sure, you don't have to take them.

SECURITY.md Outdated
### Be harmless on user environment

The PowSyBl code is executed on users environments. Using the PowSyBl code must not cause damage to the users environments.
The PowSyBl code is executed on users' environments. Using the PowSyBl code must not cause damage to the users' environments.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
The PowSyBl code is executed on users' environments. Using the PowSyBl code must not cause damage to the users' environments.
The PowSyBl code is executed in users' environments. Using the PowSyBl code must not cause damage to the users' environments.

SECURITY.md Outdated
#### Controlled dependency update

We pay attention to keep our dependency versions up-to-date and also make sure the new versions are safe. This allows PowSyBl to benefit from the latest security patches, while ensuring a protection against supply-chain attacks.
We pay attention to keeping our dependency versions up to date and also make sure the new versions are safe. This allows PowSyBl to benefit from the latest security patches, while ensuring protection against supply-chain attacks.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
We pay attention to keeping our dependency versions up to date and also make sure the new versions are safe. This allows PowSyBl to benefit from the latest security patches, while ensuring protection against supply-chain attacks.
We pay attention to keeping our dependency versions up to date and also make sure that the new versions are safe. This allows PowSyBl to benefit from the latest security patches, while ensuring protection against supply-chain attacks.

Signed-off-by: Nicolas Rol <[email protected]>
# Conflicts:
#	CONTRIBUTING.md
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.

4 participants