Merge pull request #99 from papauorg/feature/update-repo-links

Fix occurences of the repo name to reflect the PiBrewing repo

CONTRIBUTING.md

@@ -29,7 +29,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 ## Code of Conduct
 
 This project and everyone participating in it is governed by the
-[CraftBeerPi 4 Code of Conduct](https://github.com/avollkopf/craftbeerpi4/blob/master/CODE_OF_CONDUCT.md).
+[CraftBeerPi 4 Code of Conduct](https://github.com/PiBrewing/craftbeerpi4/blob/master/CODE_OF_CONDUCT.md).
 By participating, you are expected to uphold this code. Please report unacceptable behavior
 to <avollkopf@web.de>.
 
@@ -38,11 +38,11 @@ to <avollkopf@web.de>.
 
 > If you want to ask a question, we assume that you have read the available [Documentation](https://openbrewing.gitbook.io/craftbeerpi4_support/).
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/avollkopf/craftbeerpi4//issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/PiBrewing/craftbeerpi4//issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/avollkopf/craftbeerpi4//issues/new).
+- Open an [Issue](https://github.com/PiBrewing/craftbeerpi4//issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
@@ -77,7 +77,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 - Make sure that you are using the latest version.
 - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://openbrewing.gitbook.io/craftbeerpi4_support/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/avollkopf/craftbeerpi4/issues?q=label%3Abug).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/PiBrewing/craftbeerpi4/issues?q=label%3Abug).
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
   - Stack trace (Traceback)
@@ -94,7 +94,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue](https://github.com/avollkopf/craftbeerpi4//issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Open an [Issue](https://github.com/PiBrewing/craftbeerpi4//issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behavior you would expect and the actual behavior.
 - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
@@ -117,13 +117,13 @@ This section guides you through submitting an enhancement suggestion for CraftBe
 
 - Make sure that you are using the latest version.
 - Read the [documentation](https://openbrewing.gitbook.io/craftbeerpi4_support/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/avollkopf/craftbeerpi4//issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Perform a [search](https://github.com/PiBrewing/craftbeerpi4//issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 
 <!-- omit in toc -->
 #### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/avollkopf/craftbeerpi4//issues).
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/PiBrewing/craftbeerpi4//issues).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.