diff options
| author | Andrew Kelley <superjoe30@gmail.com> | 2015-06-17 13:57:30 -0700 |
|---|---|---|
| committer | Andrew Kelley <superjoe30@gmail.com> | 2015-06-17 13:58:36 -0700 |
| commit | c78005aac20f252e468be1d5f3a88bdf0fa1370e (patch) | |
| tree | 699652036eaf8465f4fef3992523a1ef3bb94a36 /CONTRIBUTING.md | |
| parent | c544a2b74bffdbf9c1bf8017f60eb294440779ca (diff) | |
| download | nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar.gz nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar.bz2 nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar.lz nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar.xz nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.tar.zst nixpkgs-c78005aac20f252e468be1d5f3a88bdf0fa1370e.zip | |
fix typos in CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 519b2180b01..195d1ae6d0a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -44,7 +44,7 @@ * _If you don't want to install pkg in you profile_. * `nix-build -A pkg-attribute-name <path to your local nixpkgs folder>/default.nix` and check results in the folder `result`. It will appear in the same directory where you did `nix-build`. * If you did `nix-env -i pkg-name` you can do `nix-env -e pkg-name` to uninstall it from your system. - * nixos and it's modules + * nixos and its modules * You can add new module to you `nixos-configuration file` (usually it's `/etc/nixos/configuration.nix`. And do `sudo nixos-rebuild test -I nixpkgs=<path to your local nixpkgs folder> --fast` * If you have commits `pkg-name: oh, forgot to insert whitespace`: squash commits in this case. Use `git rebase -i`. @@ -56,7 +56,7 @@ * Create pull request. * Write the title in format `(pkg-name | service): improvement` * If you update the pkg, write versions `from -> to` - * Write in comment if you have tested your patch. Do not rely much on `TravisCL`. + * Write in comment if you have tested your patch. Do not rely much on `TravisCI`. * If you make an improvement, write why is it good. * Notify maintainers of the package. For example add to the message: `cc @jagajaga @domenkozar` |