about summary refs log tree commit diff
diff options
context:
space:
mode:
authorArseniy Seroka <jagajaga@users.noreply.github.com>2015-06-17 23:19:01 +0200
committerArseniy Seroka <jagajaga@users.noreply.github.com>2015-06-17 23:19:01 +0200
commit97db35a3b46600e6a450320d2006e6a995e683bc (patch)
tree8610cea1302c66543ef5ada15d7c0c7901aaa110
parent84235ff763ee77058032319f791fb1d49c9695d8 (diff)
parentc78005aac20f252e468be1d5f3a88bdf0fa1370e (diff)
downloadnixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar.gz
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar.bz2
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar.lz
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar.xz
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.tar.zst
nixlib-97db35a3b46600e6a450320d2006e6a995e683bc.zip
Merge pull request #8375 from andrewrk/typos
fix typos in CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 519b2180b018..195d1ae6d0ac 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`