docs: Change all uses of JAMstack to Jamstack (#113)

* Update README.md

* Change all appearances of JAMstack to Jamstack

Co-authored-by: ajcwebdev <ac@ac.local>

README.md

@@ -1,6 +1,6 @@
 <p align="center" style="text-align:center">
   <img alt="Bison Logo" src="https://user-images.githubusercontent.com/14339/89243835-f47e7c80-d5d2-11ea-8d8d-36202227d0ec.png" />
-  <h1 align="center">The Full Stack JAMstack in-a-box.</h1>
+  <h1 align="center">The Full Stack Jamstack in-a-box.</h1>
 </p>
 
 Bison is a starter repository created out of real-world apps at [Echobind](https://echobind.com). It represents our team's "Greenfield Web Stack" that we use when creating web apps for clients.
@@ -41,7 +41,7 @@ We're always improving on this, and we welcome suggestions from the community!
 
 ## Alternatives
 
-A few other projects that are rapidly maturing in the Full Stack JAMStack space.
+A few other projects that are rapidly maturing in the Full Stack Jamstack space.
 
 **RedwoodJS**
 [Redwood](https://github.com/redwoodjs/redwood) is a very promising framework that we're watching. We took the concept of "Cells" directly from Redwood (though admittedly our version takes a bit more code!)

docs/ci.md

@@ -14,10 +14,10 @@ The Vercel project and org id, can be copied from `.vercel/project.json`. You ca
 
 After tests pass, the app will deploy. Every push will create a preview deployment. Merging to the main branch will deploy to staging, and pushing to the production branch will deploy to production.
 
-If you'd like to change these configurations to a more typical JAMstack flow (where merging to the main branch deploys to production), update the section below in `..github/workflows/main.js.yml`:
+If you'd like to change these configurations to a more typical Jamstack flow (where merging to the main branch deploys to production), update the section below in `..github/workflows/main.js.yml`:
 
 ```
-## For a typical JAMstack flow, this should be your default branch.
+## For a typical Jamstack flow, this should be your default branch.
 ## For a traditional flow that auto-deploys staging and deploys prod is as needed, keep as is
 if: github.ref != 'refs/heads/production' # every branch EXCEPT production
 ```

packages/create-bison-app/logo.js

@@ -13,6 +13,6 @@ module.exports = `
 @@@@@@%@@@@@@&%%%%%%%%&&&@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&&&%%%%%%%%&@@@@@@%%@@@@@
 @@@@@@%%%%@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@%%%%%@@@@@
 
-        The Full Stack JAMstack in-a-box. Make something awesome with it!
+        The Full Stack Jamstack in-a-box. Make something awesome with it!
                                    ♥️  Echobind
 `;

packages/create-bison-app/package.json

@@ -1,7 +1,7 @@
 {
   "name": "create-bison-app",
   "version": "1.9.14-canary.2",
-  "description": "Creates a production-ready full-stack JAMstack app",
+  "description": "Creates a production-ready full-stack Jamstack app",
   "license": "MIT",
   "repository": "echobind/bisonapp",
   "author": {

packages/create-bison-app/template/.github/workflows/main.js.yml.ejs

@@ -114,7 +114,7 @@ jobs:
     # needs: tests
 <% } -%>
 
-    ## For a typical JAMstack flow, the ref below should be your default branch.
+    ## For a typical Jamstack flow, the ref below should be your default branch.
     ## For a traditional flow that auto-deploys staging and deploys prod is as needed, keep as is
 
 <% if (host.name === 'heroku') { -%>
@@ -146,7 +146,7 @@ jobs:
     runs-on: ubuntu-latest
     # For production deploys, make sure tests pass first
     needs: tests
-    ## For a typical JAMstack flow, the ref below should be your default branch.
+    ## For a typical Jamstack flow, the ref below should be your default branch.
     ## For a traditional flow that auto-deploys staging and deploys prod is as needed, keep as is
     if: github.ref == 'refs/heads/<%= repo.productionBranch %>'
     steps: