gador/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: avoid 'simply' (#266434)

Browse Source 
While the word 'simply' is usually added to encourage readers, it often has the
opposite effect and may even appear condescending, especially when the reader
runs into trouble trying to apply the suggestions from the documentation. It is
almost always an improvement to simply drop the word from the sentence.

(there are more possible improvements like this, we can apply those in separate
PRs)
This commit is contained in:
Arnout Engelen
2023-11-09 21:48:05 +01:00
committed by GitHub
parent 3dc0248dbc
commit 97b0ae26f7
26 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/languages-frameworks/php.section.md
View File

@@ -58,7 +58,7 @@ php.withExtensions ({ enabled, all }:
++ [ all.imagick ])
```
To build your list of extensions from the ground up, you can simply
To build your list of extensions from the ground up, you can
ignore `enabled`:
```nix
@@ -140,7 +140,7 @@ Example of building `composer` with additional extensions:
### Overriding PHP packages {#ssec-php-user-guide-overriding-packages}
`php-packages.nix` form a scope, allowing us to override the packages defined
within. For example, to apply a patch to a `mysqlnd` extension, you can simply
within. For example, to apply a patch to a `mysqlnd` extension, you can
pass an overlay-style function to `php`’s `packageOverrides` argument:
```nix
@@ -191,7 +191,7 @@ using the `bin` attribute in `composer.json`, these binaries will be
automatically linked and made accessible in the derivation. In this context,
"binaries" refer to PHP scripts that are intended to be executable.
To use the helper effectively, simply add the `vendorHash` attribute, which
To use the helper effectively, add the `vendorHash` attribute, which
enables the wrapper to handle the heavy lifting.
Internally, the helper operates in three stages: