Fix typos (#100)

Found via `typos --hidden --format brief`

Author: kianmeng

lib/mix/tasks/phoenix_sync.install.ex

@@ -86,7 +86,7 @@ if Code.ensure_loaded?(Igniter) do
       if mode not in @valid_modes do
         Igniter.add_issue(
           igniter,
-          "mode #{inspect(mode)} is invlid, valid modes are: #{@valid_modes |> Enum.join(", ")}"
+          "mode #{inspect(mode)} is invalid, valid modes are: #{@valid_modes |> Enum.join(", ")}"
         )
       else
         add_dependencies(igniter, mode)

lib/phoenix/sync/electric.ex

@@ -38,7 +38,7 @@ defmodule Phoenix.Sync.Electric do
   pass the key you configure here (in this case `:config`) to the
   `Phoenix.Sync.Electric` plug in it's `init_opts`.
 
-  In your application, build your Electric confguration using
+  In your application, build your Electric configuration using
   `Phoenix.Sync.plug_opts()` and pass the result to your router as
   `phoenix_sync`:
 
@@ -447,7 +447,7 @@ defmodule Phoenix.Sync.Electric do
   end
 
   # Returns a function to generate the config so that we can
-  # centralise the test for the existance of electric.
+  # centralise the test for the existence of electric.
   # Need this because the convert_repo_config/1 function needs Electric
   # installed too
   defp validate_database_config(_env, mode, opts) do

lib/phoenix/sync/live_view.ex

@@ -101,7 +101,7 @@ if Code.ensure_loaded?(Phoenix.Component) do
 
       This event is useful to show the stream component after
       the initial sync. Because of the streaming nature of Electric Shapes, the
-      intitial sync can cause flickering as items are added, removed and updated.
+      initial sync can cause flickering as items are added, removed and updated.
 
       E.g.:
 

lib/phoenix/sync/plug.ex

@@ -6,7 +6,7 @@ defmodule Phoenix.Sync.Plug do
   Rather than configuring your [Electric Typescript
   client](https://electric-sql.com/docs/api/clients/typescript) directly, you
   instead configure a route in your application with a pre-configured
-  `Electric.Client.ShapeDefinition` and then retreive the URL and other
+  `Electric.Client.ShapeDefinition` and then retrieve the URL and other
   configuration for that shape from your client via a request to your Phoenix
   application.
 

lib/phoenix/sync/sandbox.ex

@@ -105,7 +105,7 @@ if Phoenix.Sync.sandbox_enabled?() do
         end
 
     However processes started outside of the test process tree that need to be
-    [explictly granted access to the sandboxed
+    [explicitly granted access to the sandboxed
     connection](https://hexdocs.pm/ecto_sql/Ecto.Adapters.SQL.Sandbox.html#module-allowances)
     will also need to be explicitly registered to the current test's
     replication stream using `#{inspect(__MODULE__)}.allow/3`. This calls
@@ -272,7 +272,7 @@ if Phoenix.Sync.sandbox_enabled?() do
           # we link the sandbox to the current (test) process not the connection
           # owner because that's the ownership route that works. The owner
           # is a convenience to link the repo connection to a process who's lifetime
-          # is explictly managed rather than a mechanism for linking the test
+          # is explicitly managed rather than a mechanism for linking the test
           # to the sandbox txn.
           Sandbox.StackRegistry.register(test_pid, stack_id)
 

lib/phoenix/sync/sandbox/postgres/adapter.ex

@@ -392,7 +392,7 @@ if Phoenix.Sync.sandbox_enabled?() do
         return_all = Enum.map(all_columns, &{:old, &1}) ++ Enum.map(all_columns, &{:new, &1})
 
         # https://stackoverflow.com/a/7927957
-        # return the old and new values from an update by aquiring an exclusive lock
+        # return the old and new values from an update by acquiring an exclusive lock
         # on the row and using a sub-query.
         # UPDATE table new
         #     SET value = $1

lib/phoenix/sync/writer.ex

@@ -96,7 +96,7 @@ if Code.ensure_loaded?(Ecto) do
     Phoenix already ships with primitives like `Ecto.Multi` and `c:Ecto.Repo.transaction/2`.
     However, `#{inspect(__MODULE__)}` provides:
 
-    - a number of convienience functions that simplify ingesting mutation operations
+    - a number of convenience functions that simplify ingesting mutation operations
     - a high-level pipeline that dries up a lot of common boilerplate and allows you to re-use
       your existing `Plug` and `Ecto.Changeset` logic
 
@@ -113,7 +113,7 @@ if Code.ensure_loaded?(Ecto) do
           |> #{inspect(__MODULE__)}.allow(MyApp.OtherSchema)
           |> #{inspect(__MODULE__)}.apply(transaction, Repo, format: MyApp.MutationFormat)
 
-    Or, instead of `apply/4` you can use seperate calls to `ingest/3` and then `transaction/2`.
+    Or, instead of `apply/4` you can use separate calls to `ingest/3` and then `transaction/2`.
     This allows you to ingest multiple formats, for example:
 
         {:ok, txid} =
@@ -183,7 +183,7 @@ if Code.ensure_loaded?(Ecto) do
     when the transaction syncs through. At which point the client can discard its local
     optimistic state.
 
-    A convinient way of doing this is to parse the request data into a list of
+    A convenient way of doing this is to parse the request data into a list of
     `#{inspect(__MODULE__)}.Operation`s using a `#{inspect(__MODULE__)}.Format`.
     You can then apply the changes yourself by matching on the operation data:
 
@@ -1324,7 +1324,7 @@ if Code.ensure_loaded?(Ecto) do
         {:ok, txid} =
           Repo.transaction(fn ->
             Enum.each(txn.operations, fn operation ->
-              # do something wih the given operation
+              # do something with the given operation
               # raise if something is wrong...
             end)
             # return the transaction id
@@ -1921,7 +1921,7 @@ if Code.ensure_loaded?(Ecto) do
 
     `Ecto.Multi` requires that all operation names be unique within a
     transaction. This function gives you a simple way to generate a name for your
-    own operations that is guarateed not to conflict with any other.
+    own operations that is guaranteed not to conflict with any other.
 
     Example:
 

test/phoenix/sync/application_test.exs

@@ -181,7 +181,7 @@ defmodule Phoenix.Sync.ApplicationTest do
         mode: :embedded,
         env: :dev,
         repo: Support.ConfigTestRepo,
-        # don't overwrite this explict config
+        # don't overwrite this explicit config
         storage_dir: storage_dir
       ]
 
@@ -213,7 +213,7 @@ defmodule Phoenix.Sync.ApplicationTest do
              } = Map.new(opts)
     end
 
-    test "embedded mode with explict replication_connection_opts and query_connection_opts" do
+    test "embedded mode with explicit replication_connection_opts and query_connection_opts" do
       storage_dir = Path.join([System.tmp_dir!(), "storage-dir#{System.monotonic_time()}"])
 
       config = [
@@ -260,7 +260,7 @@ defmodule Phoenix.Sync.ApplicationTest do
              } = Map.new(opts)
     end
 
-    test "embedded mode with explict connection_opts" do
+    test "embedded mode with explicit connection_opts" do
       storage_dir = Path.join([System.tmp_dir!(), "storage-dir#{System.monotonic_time()}"])
 
       config = [

test/phoenix/sync/plug_test.exs

@@ -319,7 +319,7 @@ defmodule Phoenix.Sync.PlugTest do
              }
     end
 
-    test "works with Phoenix.Router.forward/3 and paramter based shapes" do
+    test "works with Phoenix.Router.forward/3 and parameter based shapes" do
       resp =
         Phoenix.ConnTest.build_conn()
         |> Phoenix.ConnTest.get("/shape/generic", %{

test/support/live_views/stream.ex

@@ -42,7 +42,7 @@ defmodule Phoenix.Sync.LiveViewTest.StreamLive do
   end
 
   def handle_info({:sync, event}, socket) do
-    # send messsage to test pid, just for sync
+    # send message to test pid, just for sync
     send(socket.assigns.test_pid, {:sync, event})
     {:noreply, Phoenix.Sync.LiveView.sync_stream_update(socket, event)}
   end
@@ -240,7 +240,7 @@ defmodule Phoenix.Sync.LiveViewTest.StreamSandbox do
   end
 
   def handle_info({:sync, event}, socket) do
-    # send messsage to test pid, just for sync
+    # send message to test pid, just for sync
     send(socket.assigns.test_pid, {:sync, event})
     {:noreply, Phoenix.Sync.LiveView.sync_stream_update(socket, event)}
   end