]> git.madduck.net Git - etc/awesome.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

readme updated
authorLuke Bonham <dada@archlinux.info>
Tue, 27 Jun 2017 11:24:08 +0000 (13:24 +0200)
committerLuke Bonham <dada@archlinux.info>
Tue, 27 Jun 2017 11:24:08 +0000 (13:24 +0200)
README.rst

index f92a0849c24f74198cba49f94856d2fc47b60311..b8e2f55a7d4341b9c30773d773ce90206cce1d98 100644 (file)
@@ -13,22 +13,20 @@ Layouts, widgets and utilities for Awesome WM 4.x
 Description
 -----------
 
 Description
 -----------
 
-Successor of awesome-vain_, this module provides alternative layouts, asynchronous widgets and utility functions for Awesome_ WM.
-
-Read the wiki_ for all the info.
+Successor of awesome-vain_, this module provides alternative layouts, asynchronous widgets and utility functions for Awesome_ WM. Read the wiki_ for all the info.
 
 Contributions
 -------------
 
 
 Contributions
 -------------
 
-Any contribution is welcome! Feel free to make a pull request.
+Constructive criticism and suggestions are welcome.
 
 
-Just make sure that:
+If you want to create a pull request, make sure that:
 
 - Your code fits with the general style of the module. In particular, you should use the same indentation pattern that the code uses, and also avoid adding space at the ends of lines.
 
 
 - Your code fits with the general style of the module. In particular, you should use the same indentation pattern that the code uses, and also avoid adding space at the ends of lines.
 
-- Your code its easy to understand, maintainable, and modularized. You should also avoid code duplication wherever possible by adding functions or using lain.helpers_. If something is unclear, and you can't write it in such a way that it will be clear, explain it with a comment.
+- Your code its easy to understand, maintainable, and modularized. You should also avoid code duplication wherever possible by adding functions to or using lain.helpers_. If something is unclear, or you can't write it in such a way that it will be clear, explain it with a comment.
 
 
-- You test your changes before submitting to make sure that not only your code works, but did not break other parts of the module too!
+- You test your changes before submitting to make sure that you code works and does not break other parts of the module.
 
 - You eventually update ``wiki`` submodule with a thorough section.
 
 
 - You eventually update ``wiki`` submodule with a thorough section.