Docs improvement (#11)

* Add consider lints, fix bare url, update mail

* Update patch version

CODE_OF_CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at git@honzabittner.cz. All
+reported by contacting the project team at git@tenhobi.dev. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.
@@ -68,9 +68,9 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+<https://www.contributor-covenant.org/faq>

CONTRIBUTING.md

@@ -1,11 +1,10 @@
 # Contributing
 
-When contributing to this repository, please first discuss the change you wish to make via issue or any other method with the owners of this repository before making a change. 
+When contributing to this repository, please first discuss the change you wish to make via issue or any other method with the owners of this repository before making a change.
 
 Please note we have a code of conduct, please follow it in all your interactions with the project.
 
 ## Pull Request Process
 
 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
 1. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
-

README.md

@@ -32,13 +32,23 @@ Or, if you using e.g. continuous builds, they will likely fail whenever a new ve
 include: package:effective_dart/analysis_options.1.1.0.yaml
 ```
 
+## Consider lints
+
+Consider guidelines are practices that you might or might not want to follow, depending on circumstances, precedents, and your own preference.
+
+Following lints are not enforced by this package:
+
+- [`prefer_expression_function_bodies`](https://dart-lang.github.io/linter/lints/prefer_expression_function_bodies.html)
+- [`prefer_typing_uninitialized_variables`](https://dart-lang.github.io/linter/lints/prefer_typing_uninitialized_variables.html)
+- [`use_function_type_syntax_for_parameters`](https://dart-lang.github.io/linter/lints/use_function_type_syntax_for_parameters.html)
+
 ## Unused Lints
 
 Following lints have been considered and will not be enforced by this package:
 
-- `lines_longer_than_80_chars` might be practical not to follow for many people
-- `unnecessary_getters` has been [disabled](https://github.com/dart-lang/linter/issues/23)
-- `comment_references` is way too restrictive and comment references are handled in different ways in tools ([see this issue](https://github.com/dart-lang/sdk/issues/36974))
+- [`lines_longer_than_80_chars`](https://dart-lang.github.io/linter/lints/lines_longer_than_80_chars.html) might be practical not to follow for many people
+- [`unnecessary_getters`](https://dart-lang.github.io/linter/lints/unnecessary_getters.html) has been [disabled](https://github.com/dart-lang/linter/issues/23)
+- [`comment_references`](https://dart-lang.github.io/linter/lints/comment_references.html) is way too restrictive and comment references are handled in different ways in tools ([see this issue](https://github.com/dart-lang/sdk/issues/36974))
 
 ## Suppressing Lints
 

pubspec.yaml

@@ -1,7 +1,7 @@
 name: effective_dart
 description: This package provides the lints according to the Effective Dart guide.
-version: 1.1.1
-author: Honza Bittner <git@honzabittner.cz>
+version: 1.1.2
+author: Honza Bittner <git@tenhobi.cz>
 repository: https://github.com/tenhobi/effective_dart
 issue_tracker: https://github.com/tenhobi/effective_dart/issues
 homepage: https://github.com/tenhobi/effective_dart