Post-release fix-ups

CONTRIBUTING.md

@@ -15,7 +15,7 @@ Trying to figure out how to make it work? Or how to use it in your scenario?
 ## Report a Bug
 
 1.  Create a test case that reproduces the unexpected behavior
-1.  [Open a new issue with this template](https://github.com/seantimm/svelte-fontawesome/issues/new?template=bug-report.md),
+1.  [Open a new issue with this template](https://github.com/FortAwesome/svelte-fontawesome/issues/new?template=bug-report.md),
     and be sure to include a link to the reproduction you made with StackBlitz.
 
 ## Submit a Pull Request
@@ -24,8 +24,8 @@ Add tests if you add code.
 
 ## Everything Else
 
-- [Request a feature](https://github.com/seantimm/svelte-fontawesome/issues/new??title=Feature%20request:feature-name&template=feature-request.md)
-- [Request a new icon](https://github.com/seantimm/Font-Awesome/issues/new?title=Icon%20request:%20icon-name&template=icon-request.md)
+- [Request a feature](https://github.com/FortAwesome/svelte-fontawesome/issues/new??title=Feature%20request:feature-name&template=feature-request.md)
+- [Request a new icon](https://github.com/FortAwesome/Font-Awesome/issues/new?title=Icon%20request:%20icon-name&template=icon-request.md)
 
 # Project Goals
 

DEVELOPMENT.md

@@ -28,7 +28,7 @@ The following commands are available through `npm run`
 1. `npm publish --tag latest-0.2 --tag latest --registry https://npm.fontawesome.com` (publish to Pro registry)
 1. `git add . && git commit -m 'Release VERSION'`
 1. `git push`
-1. Create a [new release](https://github.com/seantimm/svelte-fontawesome/releases/new) with `CHANGELOG` details
+1. Create a [new release](https://github.com/FortAwesome/svelte-fontawesome/releases/new) with `CHANGELOG` details
 
 ## Authenticating with the npm.fontawesome.com registry
 

UPGRADING.md

@@ -4,5 +4,5 @@ See the [CHANGELOG.md](./CHANGELOG.md) for detailed information about what has c
 
 This guide is useful to figure out what you need to do between breaking changes.
 
-As always, [submit issues](https://github.com/seantimm/svelte-fontawesome/issues/new) that you run into with this guide or with these upgrades to us.
+As always, [submit issues](https://github.com/FortAwesome/svelte-fontawesome/issues/new) that you run into with this guide or with these upgrades to us.
 

examples/svelte-app-typescript/package.json

@@ -14,7 +14,7 @@
     "@fortawesome/free-brands-svg-icons": "^6.1.1",
     "@fortawesome/free-solid-svg-icons": "^6.1.1",
     "@fortawesome/pro-duotone-svg-icons": "^6.1.1",
-    "@seantimm/svelte-fontawesome": "github:seantimm/svelte-fontawesome",
+    "@fortawesome/svelte-fontawesome": "^0.2.0",
     "@sveltejs/vite-plugin-svelte": "^1.0.1",
     "@tsconfig/svelte": "^3.0.0",
     "svelte": "^3.49.0",
@@ -24,4 +24,4 @@
     "typescript": "^4.6.4",
     "vite": "^3.0.0"
   }
-}
+}

examples/svelte-app/package.json

@@ -13,9 +13,9 @@
     "@fortawesome/free-brands-svg-icons": "^6.1.1",
     "@fortawesome/free-solid-svg-icons": "^6.1.1",
     "@fortawesome/pro-duotone-svg-icons": "^6.1.1",
-    "@seantimm/svelte-fontawesome": "github:seantimm/svelte-fontawesome",
+    "@fortawesome/svelte-fontawesome": "^0.2.0",
     "@sveltejs/vite-plugin-svelte": "^1.0.1",
     "svelte": "^3.49.0",
     "vite": "^3.0.0"
   }
-}
+}

examples/sveltekit-app/package.json

@@ -11,7 +11,7 @@
 	"devDependencies": {
     "@fortawesome/fontawesome-svg-core": "^6.1.1",
     "@fortawesome/free-solid-svg-icons": "^6.1.1",
-    "@seantimm/svelte-fontawesome": "github:seantimm/svelte-fontawesome",
+    "@fortawesome/svelte-fontawesome": "^0.2.0",
 		"@sveltejs/adapter-auto": "next",
 		"@sveltejs/kit": "next",
 		"svelte": "^3.44.0",