fix: remove bad package reference from the docs

.github/workflows/elixir.yml

@@ -44,3 +44,18 @@ jobs:
         if: startsWith(github.ref, 'refs/tags/v')
         env:
           HEX_API_KEY: ${{ secrets.HEX_API_KEY }}
+      - id: log
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: echo "::set-output name=version::$(git describe --tags)"
+      - uses: ethomson/send-tweet-action@v1
+        if: startsWith(github.ref, 'refs/tags/v')
+        with:
+          status: |
+            Version "${{ steps.log.output.version }}" of Ash released!
+
+            See the changelog for more info:
+            https://github.com/ash-project/ash/blob/master/CHANGELOG.md
+          consumer-key: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
+          consumer-secret: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
+          access-token: ${{ secrets.TWITTER_ACCESS_TOKEN }}
+          access-token-secret: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}

documentation/introduction/getting_started.md

@@ -6,7 +6,7 @@ For information on creating a new Elixir application, see [this guide](https://e
 
 ## Add Ash
 
-Add `ash` to your dependencies in `mix.exs`. The latest version can be found by running `mix hex.info ash_core`.
+Add `ash` to your dependencies in `mix.exs`. The latest version can be found by running `mix hex.info ash`.
 
 ## Create an Ash API
 
@@ -23,7 +23,7 @@ end
 
 ## Create a resource
 
-A resource is the primary entity in Ash. Your Api module ties your resources together and gives them an interface, but the vast majority if your configuration will live in a resource. In your typical setup, you might have a resource per database table. For those already familiar with ecto, a resource and an ecto schema are very similar. In fact, all resources define an ecto schema under the hood. This can be leveraged when you need to do things that are not yet implemented or fall outside of the scope of Ash. The current reccomendation for where to put your resources is in `lib/resources/<resource_name>.ex`. Here are a few examples:
+A resource is the primary entity in Ash. Your Api module ties your resources together and gives them an interface, but the vast majority if your configuration will live in a resource. In your typical setup, you might have a resource per database table. For those already familiar with ecto, a resource and an ecto schema are very similar. In fact, all resources define an ecto schema under the hood. This can be leveraged when you need to do things that are not yet implemented or fall outside of the scope of Ash. The current recommendation for where to put your resources is in `lib/resources/<resource_name>.ex`. Here are a few examples:
 
 ```elixir
 # in lib/resources/tweet.ex