0.1.2+6

@@ -2,8 +2,9 @@
 
 
 * Cleaned up Android manifest.
 * Cleaned up Android manifest.
 * Changed a test name in `test_driver`.
 * Changed a test name in `test_driver`.
-* Updated description.
+* Updated the plugin description.
 * Updated `README.md`.
 * Updated `README.md`.
+* Updated `CONTRIBUTING.md`.
 * Removed unnecessary `Assets` directory from the `ios` folder.
 * Removed unnecessary `Assets` directory from the `ios` folder.
 
 
 ## 0.1.2+5
 ## 0.1.2+5

@@ -17,8 +17,10 @@ The following steps are based on [flutter/plugin's contributing guide](https://g
  * `git checkout upstream/master -b <name_of_your_branch>`
  * `git checkout upstream/master -b <name_of_your_branch>`
  * Now, you can change the code necessary for your patch.
  * Now, you can change the code necessary for your patch.
  
  
-   Make sure that you bump the version in [`pubspec.yaml`](https://github.com/creativecreatorormaybenot/wakelock/blob/master/pubspec.yaml) and add an entry to [`CHANGELOG.md`](https://github.com/creativecreatorormaybenot/wakelock/blob/master/CHANGELOG.md).  
-   The version format is `r.M.m+p`. You will want to increment one of these values and which one you increment depends on the impact of your patch: `p` for simple patches, `m` for minor versions, `M` for major versions, and `r` for released. Do not forget to reset the values to the right of the value you incremented to 0. You should omit `+0`.
+   Make sure that you bump the version in [`pubspec.yaml`](https://github.com/creativecreatorormaybenot/wakelock/blob/master/pubspec.yaml) 
+   and add an entry to [`CHANGELOG.md`](https://github.com/creativecreatorormaybenot/wakelock/blob/master/CHANGELOG.md).  
+   The version format is `r.M.m+p`. You will want to increment one of these values and which one you increment depends on the impact of your patch: 
+   `p` for simple patches, `m` for minor versions, `M` for major versions, and `r` for released. Do not forget to reset the values to the right of the value you incremented to 0. You should omit `+0`.
  * `git commit -am "<commit_message>"`
  * `git commit -am "<commit_message>"`
  * `git push origin <name_of_your_branch>`
  * `git push origin <name_of_your_branch>`
 
 
@@ -31,7 +33,8 @@ Alternatively, you can also use `git pull-request` via [GitHub hub](https://hub.
  * You should remember to exclude all files and directories your IDE might generate using the `.gitignore` files (if they do not already contain them for your IDE).  
  * You should remember to exclude all files and directories your IDE might generate using the `.gitignore` files (if they do not already contain them for your IDE).  
    If you feel like you can make useful additions to any of the `.gitignore` files, you can include them in your pull request, potentially with an explanation.
    If you feel like you can make useful additions to any of the `.gitignore` files, you can include them in your pull request, potentially with an explanation.
 
 
- * It is probably easier for you to run the integration tests for the plugin locally using `flutter drive --target=test_driver/app.dart` in the `example` directory before opening a pull request (CI also runs the integration tests).  
+ * It is probably easier for you to run the integration tests for the plugin locally using `flutter drive --target=test_driver/app.dart` in the `example` directory 
+   before opening a pull request (CI also runs the integration tests).  
    This way you can ensure that any changes you have made work properly. Furthermore, you might also want to add some tests if you implement new functionality.
    This way you can ensure that any changes you have made work properly. Furthermore, you might also want to add some tests if you implement new functionality.
 
 
  * You should also run `flutter format lib example --fix` in the root directory and make sure that `flutter analyze` does not report any errors. 
  * You should also run `flutter format lib example --fix` in the root directory and make sure that `flutter analyze` does not report any errors.