Chore: typo fixes

Author: georgesittas

docs/guides/notifications.md

@@ -130,7 +130,7 @@ This example stops all notifications other than those for `User1`:
 
 SQLMesh notifications are triggered by events. The events that should trigger a notification are specified in the notification target's `notify_on` field.
 
-Notifications are support for [`plan` application](../concepts/plans.md) start/end/failure, [`run`](../reference/cli.md#run) start/end/failure, and [`audit`](../concepts/audits.md) failures.
+Notifications are supported for [`plan` application](../concepts/plans.md) start/end/failure, [`run`](../reference/cli.md#run) start/end/failure, and [`audit`](../concepts/audits.md) failures.
 
 For `plan` and `run` start/end, the target environment name is included in the notification message. For failures, the Python exception or error text is included in the notification message.
 

docs/guides/scheduling.md

@@ -1,6 +1,6 @@
 # Scheduling guide
 
-SQLMesh currently offers three ways of scheduling model evaluation:
+SQLMesh currently offers two ways of scheduling model evaluation:
 
 * Using [SQLMesh's built-in scheduler](#built-in-scheduler)
 * Using [Tobiko Cloud](../cloud/features/scheduler/scheduler.md)

docs/guides/signals.md

@@ -28,7 +28,7 @@ Signal checking functions examines a batch of time intervals. The function is al
 
 To define a signal, create a `signals` directory in your project folder. Define your signal in a file named `__init__.py` in that directory (you can have additional python file names as well).
 
-A signal is a function that accepts a batch (DateTimeRanges: t.List[t.Tuple[datetime, datetime]]) and returns a batch or a boolean. It needs use the @signal decorator.
+A signal is a function that accepts a batch (`DateTimeRanges: t.List[t.Tuple[datetime, datetime]]`) and returns a batch or a boolean. It needs to use the `@signal` decorator.
 
 We now demonstrate signals of varying complexity.