Update README.md

README.md

@@ -1,4 +1,4 @@
-![build-test](https://github.com/jwgmeligmeyling/checkstyle-github-action/workflows/build-test/badge.svg)
+![build-test](https://github.com/lcollins/checkstyle-github-action/workflows/build-test/badge.svg)
 
 # Checkstyle GitHub Action
 
@@ -48,7 +48,7 @@ jobs:
           ${{ runner.os }}-maven-
     - name: Build with Maven
       run: mvn -B verify checkstyle:checkstyle
-    - uses: jwgmeligmeyling/checkstyle-github-action@master
+    - uses: lcollins/checkstyle-github-action@master
       with:
         path: '**/checkstyle-result.xml'
 ```
@@ -84,14 +84,14 @@ Even for `pull_request` events there is the possibility to checkout the pull req
 ## Other relevant actions
 This is a Github Action in a series of other GitHub Actions. Similar actions include:
 
-* [checkstyle-github-action](https://github.com/jwgmeligmeyling/checkstyle-github-action)
-* [pmd-github-action](https://github.com/jwgmeligmeyling/pmd-github-action)
-* [spotbugs-github-action](https://github.com/jwgmeligmeyling/spotbugs-github-action)
+* [checkstyle-github-action](https://github.com/lcollins/checkstyle-github-action)
+* [pmd-github-action](https://github.com/lcollins/pmd-github-action)
+* [spotbugs-github-action](https://github.com/lcollins/spotbugs-github-action)
 
 ## Known limitations
 Due to GitHub API limitations, we cannot specify to which Workflow Run (or underlying Check Suite) a newly created Check Run should be associated.
 As a result, workflows that trigger on several types of events, might push results under another event than the action was run in.
-For more information, see: https://github.com/jwgmeligmeyling/checkstyle-github-action/issues/2
+For more information, see: https://github.com/lcollins/checkstyle-github-action/issues/2
 
 ## Contributing