Spelling

.github/ISSUE_TEMPLATE.md

@@ -10,7 +10,7 @@ This template isn't a strict requirement to open issues, but please try to provi
 
 ### Steps to reproduce the behavior
 
-If the issue can be reproduced using a [mirror context](http://zio.dev/zio-quill/contexts#mirror-context), please provide a scastie snippet that reproduces it. See https://scastie.scala-lang.org/fwbrasil/Z2CeR2qHQJK6EyQWUBhANA as an example. Remember to select the correct Quill version in the left menu.
+If the issue can be reproduced using a [mirror context](https://zio.dev/zio-quill/contexts#mirror-context), please provide a scastie snippet that reproduces it. See https://scastie.scala-lang.org/fwbrasil/Z2CeR2qHQJK6EyQWUBhANA as an example. Remember to select the correct Quill version in the left menu.
 
 ### Workaround
 

CODE_OF_CONDUCT.md

@@ -68,7 +68,7 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+available at [https://contributor-covenant.org/version/1/4][version]
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

README.md

@@ -7,7 +7,7 @@
 
 # ZIO Quill
 
-Quill provides a Quoted Domain Specific Language ([QDSL](http://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)) to express queries in Scala and execute them in a target language. 
+Quill provides a Quoted Domain Specific Language ([QDSL](https://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)) to express queries in Scala and execute them in a target language. 
 
 [![Production Ready](https://img.shields.io/badge/Project%20Stage-Production%20Ready-brightgreen.svg)](https://github.com/zio/zio/wiki/Project-Stages) ![CI Badge](https://github.com/zio/zio-quill/workflows/CI/badge.svg) [![Sonatype Releases](https://img.shields.io/nexus/r/https/oss.sonatype.org/io.getquill/quill-core_2.12.svg?label=Sonatype%20Release)](https://oss.sonatype.org/content/repositories/releases/io/getquill/quill-core_2.12/) [![Sonatype Snapshots](https://img.shields.io/nexus/s/https/oss.sonatype.org/io.getquill/quill-core_2.12.svg?label=Sonatype%20Snapshot)](https://oss.sonatype.org/content/repositories/snapshots/io/getquill/quill-core_2.12/) [![javadoc](https://javadoc.io/badge2/io.getquill/zio-quill-docs_2.12/javadoc.svg)](https://javadoc.io/doc/io.getquill/zio-quill-docs_2.12) [![ZIO Quill](https://img.shields.io/github/stars/zio/zio-quill?style=social)](https://github.com/zio/zio-quill)
 
@@ -71,11 +71,11 @@ You can notify all current maintainers using the handle `@getquill/maintainers`.
 
 ## Acknowledgement
 
-The project was created having Philip Wadler's talk ["A practical theory of language-integrated query"](http://www.infoq.com/presentations/theory-language-integrated-query) as its initial inspiration. The development was heavily influenced by the following papers:
+The project was created having Philip Wadler's talk ["A practical theory of language-integrated query"](https://www.infoq.com/presentations/theory-language-integrated-query) as its initial inspiration. The development was heavily influenced by the following papers:
 
-* [A Practical Theory of Language-Integrated Query](http://homepages.inf.ed.ac.uk/slindley/papers/practical-theory-of-linq.pdf)
-* [Everything old is new again: Quoted Domain Specific Languages](http://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)
-* [The Flatter, the Better](http://db.inf.uni-tuebingen.de/staticfiles/publications/the-flatter-the-better.pdf)
+* [A Practical Theory of Language-Integrated Query](https://homepages.inf.ed.ac.uk/slindley/papers/practical-theory-of-linq.pdf)
+* [Everything old is new again: Quoted Domain Specific Languages](https://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)
+* [The Flatter, the Better](https://db.inf.uni-tuebingen.de/staticfiles/publications/the-flatter-the-better.pdf)
 
 ## License
 

build.sbt

@@ -931,7 +931,7 @@ lazy val releaseSettings = Seq(
   homepage := Some(url("https://zio.dev/zio-quill/")),
   licenses := List(("Apache License 2.0", url("http://www.apache.org/licenses/LICENSE-2.0"))),
   developers := List(
-    Developer("fwbrasil", "Flavio W. Brasil", "", url("http://github.com/fwbrasil")),
+    Developer("fwbrasil", "Flavio W. Brasil", "", url("https://github.com/fwbrasil")),
     Developer("deusaquilus", "Alexander Ioffe", "", url("https://github.com/deusaquilus"))
   ),
   scmInfo := Some(
@@ -963,11 +963,11 @@ lazy val docs = project
          |</p>
          |""".stripMargin,
     readmeAcknowledgement :=
-      """|The project was created having Philip Wadler's talk ["A practical theory of language-integrated query"](http://www.infoq.com/presentations/theory-language-integrated-query) as its initial inspiration. The development was heavily influenced by the following papers:
+      """|The project was created having Philip Wadler's talk ["A practical theory of language-integrated query"](https://www.infoq.com/presentations/theory-language-integrated-query) as its initial inspiration. The development was heavily influenced by the following papers:
          |
-         |* [A Practical Theory of Language-Integrated Query](http://homepages.inf.ed.ac.uk/slindley/papers/practical-theory-of-linq.pdf)
-         |* [Everything old is new again: Quoted Domain Specific Languages](http://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)
-         |* [The Flatter, the Better](http://db.inf.uni-tuebingen.de/staticfiles/publications/the-flatter-the-better.pdf)""".stripMargin,
+         |* [A Practical Theory of Language-Integrated Query](https://homepages.inf.ed.ac.uk/slindley/papers/practical-theory-of-linq.pdf)
+         |* [Everything old is new again: Quoted Domain Specific Languages](https://homepages.inf.ed.ac.uk/wadler/papers/qdsl/qdsl.pdf)
+         |* [The Flatter, the Better](https://db.inf.uni-tuebingen.de/staticfiles/publications/the-flatter-the-better.pdf)""".stripMargin,
     readmeMaintainers :=
       """|- @deusaquilus (lead maintainer)
          |- @fwbrasil (creator)

build/m1/README.MD

@@ -3,7 +3,7 @@ In order to get this project to build on a Mac with an M1 or later chip, you wil
 
 1. Ensure your Docker Desktop has enough resources.  We recommend you set it for at least 4 CPUs and 8.25GB of RAM.  Anything less will likely result in mysterious hangs/crashes and much wailing and gnashing of teeth during the build process.
     ![docker-resources.png](docker-resources.png)
-2. Enable the Experimental 'Big Sur Virtualization'.  Doing so will reduce your build time by nearly 1 hour!  On a Macbook Air with 16gb of ram and the 1st gen M1 chip - the build (w/o codegen) should take around 25 minutes give or take with this setting enabled.
+2. Enable the Experimental 'Big Sur Virtualization'.  Doing so will reduce your build time by nearly 1 hour!  On a MacBook Air with 16gb of ram and the 1st gen M1 chip - the build (w/o codegen) should take around 25 minutes give or take with this setting enabled.
     ![img.png](experimental.png)
 3. Use the `docker-compose-m1.yml` file instead of the default `docker-compose.yml` - this adjusts the platform where necessary to match up with the ARM based M1 chip.
 
@@ -28,7 +28,7 @@ Be nice to your M1 system - stop your services - don't down them.  Running `dock
 If you plan to have some rapid build/test cycles - run: `docker-compose -f docker-compose-m1.yml stop` to stop your services.  It will preserve the volumes that were created when you ran setup.  It'll save you a good amount of time. 
 
 ## Build With a Specific Scala Version
-By default the build executes with Scala 2.13.  Not horrible - but if you want to take advantage of the improved compiler of a more recent 2.x verison of Scala you can specify that!
+By default the build executes with Scala 2.13.  Not horrible - but if you want to take advantage of the improved compiler of a more recent 2.x version of Scala you can specify that!
 You can simply set the `quill.scala.version` when you start your build:
 
 `docker-compose -f docker-compose-m1.yml run sbt sbt -Dquill.scala.version=2.13.6 -Dmodules=db test`

build/release.sh

@@ -127,7 +127,7 @@ then
         if [[ $ARTIFACT == "publish" ]]; then echo "No-Op Publish for Non Release Snapshot Branch"; fi
     else
         VERSION_FILE=$(cat version.sbt)
-        echo "Github actions branch was: ${BRANCH} and version file is $VERSION_FILE. Not Sure what to do."
+        echo "GitHub actions branch was: ${BRANCH} and version file is $VERSION_FILE. Not Sure what to do."
     fi
 else
   echo "PULL_REQUEST is not 'false' ($PULL_REQUEST). Not doing a release."

build/setup_db_scripts.sh

@@ -133,7 +133,7 @@ function setup_sqlserver() {
     /opt/mssql-tools/bin/sqlcmd -S $1 -U SA -P "QuillRocks!" -d quill_test -i $2
 }
 
-# Do a simple necat poll to make sure the oracle database is ready.
+# Do a simple netcat poll to make sure the oracle database is ready.
 # All internal database creation and schema setup scripts are handled
 # by the container and docker-compose steps.
 

docs/CONTRIBUTING.md

@@ -167,18 +167,18 @@ Finally, you can use `sbt` locally.
 
 ### All In One ###
 
-To restart the database services, rebuild them, and start with locally explosed ports run:
+To restart the database services, rebuild them, and start with locally exposed ports run:
 
 docker-compose down && docker-compose build && docker-compose run --rm --service-ports setup
 
 Note: Make sure you have exposed all the ports as mentioned above.
 
-## Debugging using Intellij
+## Debugging using IntelliJ
 
-[Intellij](https://www.jetbrains.com/idea/) has a comprehensive debugger that also works with macros which is very
-helpful when working on Quill. There are two ways to debug Quill macros using Intellij. The first way is to launch SBT in 
-debug mode and use Intellij to remote debug it. The second way is to launch a debug session 
-from Intellij from the "Run/Debug Configurations" menu.
+[IntelliJ](https://www.jetbrains.com/idea/) has a comprehensive debugger that also works with macros which is very
+helpful when working on Quill. There are two ways to debug Quill macros using IntelliJ. The first way is to launch SBT in 
+debug mode and use IntelliJ to remote debug it. The second way is to launch a debug session 
+from IntelliJ from the "Run/Debug Configurations" menu.
 
 ### Debug Macros by Remote Debugging SBT
 
@@ -190,10 +190,10 @@ After this you need to launch sbt with `sbt -jvm-debug 5005`. Note that since th
 recommended to launch sbt with additional memory, i.e. `sbt -jvm-debug 5005 -mem 4096` otherwise sbt may complain about
 having memory issues.
 
-Then in Intellij you need to
+Then in IntelliJ you need to
 [add a remote configuration](https://www.jetbrains.com/help/idea/run-debug-configuration-remote-debug.html). The default
 parameters will work fine (note that we started sbt with the debug port `5005` which is also the default debug port
-in Intellij). After you have added the configuration you should be able to start it to start debugging! Feel to free
+in IntelliJ). After you have added the configuration you should be able to start it to start debugging! Feel to free
 to add breakpoints to step through the code.
 
 Note that its possible to debug macros (you can even
@@ -204,12 +204,12 @@ invocations are cached on a file basis. You can easily do this just by adding ne
 ### Debug Macros by Launching a Session
 
 Firstly, you will need to build Quill with some additional dependencies that include the file `scala.tools.nsc.Main`.
-You can do this adding the argument `-DdebugMacro=true` to the sbt launcher. You can do this in the Intellij SBT
+You can do this adding the argument `-DdebugMacro=true` to the sbt launcher. You can do this in the IntelliJ SBT
 menu:
 
-![Intellij-SBT-Settings.png](etc/Intellij-SBT-Settings.png)
+![IntelliJ-SBT-Settings.png](etc/IntelliJ-SBT-Settings.png)
 
-In Intellij, go to `Run -> Edit Configurations...` click on the Plus (i.e. `+`) button (or `Add New Configuration`) 
+In IntelliJ, go to `Run -> Edit Configurations...` click on the Plus (i.e. `+`) button (or `Add New Configuration`) 
 and select `Application`. Then enter the following settings:
 
 ```
@@ -222,12 +222,12 @@ Build, no error check (make sure to set this since you will frequently want to d
 ```
 
 It should look like this:
-![Intellij-Run-Debug-Config.png](etc/Intellij-Run-Debug-Config.png)
+![IntelliJ-Run-Debug-Config.png](etc/IntelliJ-Run-Debug-Config.png)
 
 > NOTE In this example, our entry-point into Quill-macro-debugging is `MySqlTest.scala`.
-> In our Intellij application configuration this file name is being explicitly specified.<br /> 
+> In our IntelliJ application configuration this file name is being explicitly specified.<br /> 
 > If you wish to easily be able to macro-debug multiple entry-point files, an alternative method would be to
-> use some Intellij variables to automatically pass whatever file is currently selected. You can do this by using
+> use some IntelliJ variables to automatically pass whatever file is currently selected. You can do this by using
 > the configuration:
 > ```
 > -cp $FileFQPackage$$FileName$ $FilePath$
@@ -254,26 +254,26 @@ object MySqlTest {
 ```
 
 Set a breakpoint anywhere in the Quill codebase and run this configuration from the top-right menu shortcut:
-![Intellij-Debug-App-Launcher](etc/Intellij-Debug-App-Launcher.png)
+![IntelliJ-Debug-App-Launcher](etc/IntelliJ-Debug-App-Launcher.png)
 
 ## Additional Debug Arguments
 
 Some additional arguments you can add to your compiler's VM args provide insight into Quill's compilation:
 
 ```
--DdebugMacro=true                              // Enables libraries needed to debug via an Intellij Application session (default=false)
+-DdebugMacro=true                              // Enables libraries needed to debug via an IntelliJ Application session (default=false)
 -DexcludeTests=false                           // Excludes testing code from being build. Useful during development times that require rapid iteration
 -Dquill.macro.log.pretty=true                  // Pretty print the SQL Queries that Quill produces (default=false)
--Dquill.macro.log=true                         // Enable/Disable priting of the SQL Queries Quill generates during compile-time (default=true)
+-Dquill.macro.log=true                         // Enable/Disable printing of the SQL Queries Quill generates during compile-time (default=true)
 -Dquill.trace.enabled=true                     // Global switch that Enables/Disables printing of Quill ASTs during compilation (default=false)
 -Dquill.trace.color=true                       // Print Quill ASTs in color (default=false) 
 -Dquill.trace.opinion=false                    // Print the parts of Quill ASTs not directly used in the main transformation phases (called Opinions).  (default=false) 
 -Dquill.trace.ast.simple=true                  // Print the raw Quill ASTs elements or a more compact view of the AST code (think `show` vs `showRaw` in Scala macros). (default=true) 
 -Dquill.trace.types=sql,standard,alias,norm    // What parts of the Quill transformations to print during compilation?
 ```
 
-In Intellij, add them in the SBT settings if your are compiling using SBT:
-![Intellj-SBT-Settings-Additional.png](etc/Intellj-SBT-Settings-Additional.png)
+In IntelliJ, add them in the SBT settings if your are compiling using SBT:
+![IntelliJ-SBT-Settings-Additional.png](etc/IntelliJ-SBT-Settings-Additional.png)
 
 ## 'Trick' Debugging via the Dynamic Query API
 

docs/additional-resources.md

@@ -38,13 +38,13 @@ Please refer to [CASSANDRA.md](https://github.com/getquill/quill/blob/master/CAS
 
 ### Blog posts
 
-- **[Intro]** Haoyi's Programming Blog - [Working with Databases using Scala and Quill](http://www.lihaoyi.com/post/WorkingwithDatabasesusingScalaandQuill.html)
+- **[Intro]** Haoyi's Programming Blog - [Working with Databases using Scala and Quill](https://www.lihaoyi.com/post/WorkingwithDatabasesusingScalaandQuill.html)
 - Juliano Alves's Blog - [Streaming all the way with ZIO, Doobie, Quill, http4s and fs2](https://juliano-alves.com/2020/06/15/streaming-all-the-way-zio-doobie-quill-http4s-fs2/)
 - Juliano Alves's Blog - [Quill: Translating Boolean Literals](https://juliano-alves.com/2020/09/14/quill-translating-boolean-literals/)
 - Juliano Alves's Blog - [Quill NDBC Postgres: A New Async Module](https://juliano-alves.com/2019/11/29/quill-ndbc-postgres-a-new-async-module/)
 - Juliano Alves's Blog - [Contributing to Quill, a Pairing Session](https://juliano-alves.com/2019/11/18/contributing-to-quill-a-pairing-session/)
 - Medium @ Fwbrasil - [quill-spark: A type-safe Scala API for Spark SQL](https://medium.com/@fwbrasil/quill-spark-a-type-safe-scala-api-for-spark-sql-2672e8582b0d)
-- Scalac.io blog - [Compile-time Queries with Quill](http://blog.scalac.io/2016/07/21/compile-time-queries-with-quill.html)
+- Scalac.io blog - [Compile-time Queries with Quill](https://web.archive.org/web/20170512003505/https://blog.scalac.io/2016/07/21/compile-time-queries-with-quill.html)
 
 ## Code of Conduct