fix typo in "packages".

relvacode · Jan 17, 2024 · 3c7001d · 3c7001d
1 parent 4054bf3
commit 3c7001d
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/website/docs/README.md b/website/docs/README.md
@@ -33,7 +33,7 @@ Bob's philosophy centers around the following:
 
 ## 1. Query Builder
 
-Bob can be used to build queries, this is similar to other pacakges like [squirrel](https://github.com/Masterminds/squirrel) and [goqu](https://github.com/doug-martin/goqu)
+Bob can be used to build queries, this is similar to other packages like [squirrel](https://github.com/Masterminds/squirrel) and [goqu](https://github.com/doug-martin/goqu)
 
 However, Bob strives to be fully spec compliant. As a result, you can build **almost any** query permitted by the dialect. And because the query builders are custom crafted for each dialect. You are almost unable to build an invalid query.
 

diff --git a/website/docs/query-builder/mysql/how-to-use.md b/website/docs/query-builder/mysql/how-to-use.md
@@ -7,7 +7,7 @@ description: Supported features
 
 # How to Use
 
-Import the `mysql` package and the query mod pacakges for the different query types
+Import the `mysql` package and the query mod packages for the different query types
 
 ```go
 import (

diff --git a/website/docs/query-builder/psql/how-to-use.md b/website/docs/query-builder/psql/how-to-use.md
@@ -7,7 +7,7 @@ description: Supported features
 
 # How to Use
 
-Import the `psql` package and the query mod pacakges for the different query types
+Import the `psql` package and the query mod packages for the different query types
 
 ```go
 import (

diff --git a/website/docs/query-builder/sqlite/how-to-use.md b/website/docs/query-builder/sqlite/how-to-use.md
@@ -7,7 +7,7 @@ description: Supported features
 
 # How to Use
 
-Import the `sqlite` package and the query mod pacakges for the different query types
+Import the `sqlite` package and the query mod packages for the different query types
 
 ```go
 import (

diff --git a/website/vs/ent.md b/website/vs/ent.md
@@ -10,7 +10,7 @@ sidebar_position: 2
 
 * **Ent** is code-first. The schema is defined in code and it then generates the entities using Ent-specific techniques. If you use a different tool for migration, you then have to manually ensure that your Ent schema is in sync with your database.
 
-* **Bob** is database-first. You generate your database using the first class tools for your DB (SQL, pgAdmin, migration pacakges). And then generate your models from your database.
+* **Bob** is database-first. You generate your database using the first class tools for your DB (SQL, pgAdmin, migration packages). And then generate your models from your database.
 
 ## Query Building
 

diff --git a/website/vs/gorm.md b/website/vs/gorm.md
@@ -10,7 +10,7 @@ sidebar_position: 1
 
 * **GORM** is code-first. It generates the database from your code, using GORM-specific techniques. If you use a different tool for migration, you then have to manually ensure that your GORM models are in sync with your database.
 
-* **Bob** is database-first. You generate your database using the first class tools for your DB (SQL, pgAdmin, migration pacakges). And then generate your models from your database.
+* **Bob** is database-first. You generate your database using the first class tools for your DB (SQL, pgAdmin, migration packages). And then generate your models from your database.
 
 ## Type Safety