update rel notes

mythz · mythz · commit fed804bdec4c · 2024-09-12T22:44:45.000+08:00
diff --git a/MyApp/_pages/background-jobs.md b/MyApp/_pages/background-jobs.md
@@ -10,7 +10,7 @@ Durable Background Jobs and Scheduled Tasks for .NET 8 Apps
 
 ### Durable and Infrastructure-Free
 
-Prior to Jobs we've been using [Background MQ](/background-mq) for executing
+Prior to Background Jobs we've been using [Background MQ](/background-mq) for executing
 our background tasks which lets you queue any Request DTO to execute its API in a background worker.
 It's been our preferred choice as it didn't require any infrastructure dependencies since its concurrent
 queues are maintained in memory, this also meant they were non-durable that didn't survive across App restarts. 
@@ -20,19 +20,19 @@ designed for the task.
 
 #### SQLite Persistence
 
-We decided on using SQLite as the backing store for durable jobs since it's low latency, 
+It uses SQLite as the backing store for its durability since it's low latency, 
 [fast disk persistence](https://www.sqlite.org/fasterthanfs.html) and embeddable file-based 
-database makes it ideally suited for the task which allows creation of naturally partitionable 
-and archivable monthly databases on-the-fly without any additional admin overhead or external
-infrastructure dependencies making it an easy add-on into any .NET App without impacting or 
-adding load to its existing configured databases.
+database makes it ideally suited for the task which allows creation of naturally partition-able 
+and archivable monthly databases on-the-fly without any maintenance overhead or infrastructure 
+dependencies making it easy to add to any .NET App without impacting or adding increased load to 
+their existing configured databases.
 
 ### Queue APIs or Commands
 
-To enable even better reuse of ServiceStack APIs you're able to queue your existing ServiceStack APIs
-as a background job in addition to [Commands](/commands) added in the 
-[last v8.3 release](/releases/v8_03) used for encapsulating units of logic
-that can be used as internal invokable, inspectable and auto-retryable building blocks.
+For even greater reuse you're able to queue your existing ServiceStack APIs
+as a Background Job in addition to [Commands](/commands) added in the 
+[last v8.3 release](/releases/v8_03) for encapsulating units of logic
+into internal invokable, inspectable and auto-retryable building blocks.
 
 ### Real Time Admin UI
 
@@ -105,8 +105,8 @@ Existing .NET 8 Projects can configure their app to use **ServiceStack.Jobs** by
 x mix jobs
 :::
 
-Which adds the `Configure.BackgroundJobs.cs` [Modular Startup](/modular-startup)
-configuration and **ServiceStack.Jobs** Reference to your project.
+Which adds the `Configure.BackgroundJobs.cs` [Modular Startup](https://docs.servicestack.net/modular-startup)
+configuration and a **ServiceStack.Jobs** NuGet package reference to your project.
 
 ## Usage
 
@@ -182,11 +182,14 @@ the following options:
 
 ### Schedule Recurring Tasks
 
+In addition to queueing jobs to run in the background, it also supports scheduling recurring tasks 
+to execute APIs or Commands at fixed intervals.
+
 :::youtube DtB8KaXXMCM
 Schedule your Reoccurring Tasks with Background Jobs!
 :::
 
-APIs and Commands can be scheduled to run at either a `TimeSpan` or 
+APIs and Commands can be scheduled to run at either a `TimeSpan` or
 [CRON Expression](https://github.com/HangfireIO/Cronos?tab=readme-ov-file#cron-format) interval, e.g:
 
 ```csharp
@@ -203,7 +206,7 @@ jobs.RecurringApi(Schedule.Interval(TimeSpan.FromMinutes(1)), new CheckUrls {
 });
 ```
 
-Scheduled Tasks can be registered with an optional task name and custom Background Options, e.g: 
+That can be registered with an optional **Task Name** and **Background Options**, e.g:
 
 ```csharp
 jobs.RecurringCommand<CheckUrlsCommand>("Check URLs", Schedule.EveryMinute, 
@@ -212,14 +215,18 @@ jobs.RecurringCommand<CheckUrlsCommand>("Check URLs", Schedule.EveryMinute,
    });
 ```
 
-If no task name is provided, the Command Name or APIs Request DTO will be used. 
+:::info
+If no name is provided, the Command's Name or APIs Request DTO will be used
+:::
 
-Scheduled Tasks are idempotent where the same registration with the same name will 
+Scheduled Tasks are idempotent where the same registration with the same name will
 either create or update the scheduled task registration without losing track of the
 last time the Recurring Task was run which is also viewable in the Jobs Admin UI:
 
 ![](/img/pages/jobs/jobs-scheduled-tasks-last-job.webp)
 
+As such it's recommended to always define your App's Scheduled Tasks on Startup:
+
 ### Executing non-durable jobs
 
 `IBackgroundJobs` also supports `RunCommand` methods to be able to execute jobs transiently 
diff --git a/MyApp/_pages/releases/v8_04.md b/MyApp/_pages/releases/v8_04.md
@@ -4,10 +4,10 @@ title: ServiceStack v8.4
 
 ![](/img/pages/release-notes/v8.4/bg-sqlite.webp)
 
-We're happy to announce **ServiceStack.Jobs** our effortless solution for queueing and managing 
+We're excited to announce **Background Jobs** our effortless solution for queueing and managing 
 background jobs and scheduled tasks in any .NET 8 App, implemented in true ServiceStack fashion
-where it seamlessly integrates into existing ServiceStack Apps with a [built-in](/auto-ui) Management UI
-to provide real-time monitoring, inspection and management of background jobs.
+where it seamlessly integrates into existing Apps and call existing APIs and sports a 
+[built-in](https://servicestack.net/auto-ui) Management UI to provide real-time monitoring, inspection and management of background jobs.
 
 <p class="hide-h2"></p>
 
@@ -25,10 +25,9 @@ to provide real-time monitoring, inspection and management of background jobs.
 </div>
 </div>
 
-
 ### Durable and Infrastructure-Free
 
-Prior to Jobs we've been using [Background MQ](/background-mq) for executing
+Prior to Background Jobs we've been using [Background MQ](/background-mq) for executing
 our background tasks which lets you queue any Request DTO to execute its API in a background worker.
 It's been our preferred choice as it didn't require any infrastructure dependencies since its concurrent
 queues are maintained in memory, this also meant they were non-durable that didn't survive across App restarts. 
@@ -38,19 +37,19 @@ designed for the task.
 
 #### SQLite Persistence
 
-We decided on using SQLite as the backing store for durable jobs since it's low latency, 
+It uses SQLite as the backing store for its durability since it's low latency, 
 [fast disk persistence](https://www.sqlite.org/fasterthanfs.html) and embeddable file-based 
-database makes it ideally suited for the task which allows creation of naturally partitionable 
-and archivable monthly databases on-the-fly without any additional admin overhead or external
-infrastructure dependencies making it an easy add-on into any .NET App without impacting or 
-adding load to its existing configured databases.
+database makes it ideally suited for the task which allows creation of naturally partition-able 
+and archivable monthly databases on-the-fly without any maintenance overhead or infrastructure 
+dependencies making it easy to add to any .NET App without impacting or adding increased load to 
+their existing configured databases.
 
 ### Queue APIs or Commands
 
-To enable even better reuse of ServiceStack APIs you're able to queue your existing ServiceStack APIs
-as a background job in addition to [Commands](/commands) added in the 
-[last v8.3 release](/releases/v8_03) used for encapsulating units of logic
-that can be used as internal invokable, inspectable and auto-retryable building blocks.
+For even greater reuse you're able to queue your existing ServiceStack APIs
+as a Background Job in addition to [Commands](/commands) added in the 
+[last v8.3 release](/releases/v8_03) for encapsulating units of logic
+into internal invokable, inspectable and auto-retryable building blocks.
 
 ### Real Time Admin UI
 
@@ -80,7 +79,7 @@ Cancel Running jobs and Requeue failed jobs
 
 ### Feature Overview
 
-Despite being a v1 release it packs all the features we wanted to use in a Background Jobs solution including:
+Even in its v1 release it packs all the features we wanted in a Background Jobs solution:
 
  - No infrastructure dependencies
    - Monthly archivable rolling Databases with full Job Execution History
@@ -101,8 +100,7 @@ Despite being a v1 release it packs all the features we wanted to use in a Backg
  - Execute transitive (i.e. non-durable) jobs using named workers
  - Attach optional `Tag`, `BatchId`, `CreatedBy`, `ReplyTo` and `Args` with Jobs
 
-Please [let us know](https://servicestack.net/ideas) if there are any other missing features
-you would love to see implemented.
+Please [let us know](https://servicestack.net/ideas) of any other missing features you'd love to see implemented.
 
 ## Install
 
@@ -123,8 +121,8 @@ Existing .NET 8 Projects can configure their app to use **ServiceStack.Jobs** by
 x mix jobs
 :::
 
-Which adds the `Configure.BackgroundJobs.cs` [Modular Startup](/modular-startup)
-configuration and **ServiceStack.Jobs** Reference to your project.
+Which adds the `Configure.BackgroundJobs.cs` [Modular Startup](https://docs.servicestack.net/modular-startup)
+configuration and a **ServiceStack.Jobs** NuGet package reference to your project.
 
 ## Usage
 
@@ -200,11 +198,14 @@ the following options:
 
 ### Schedule Recurring Tasks
 
+In addition to queueing jobs to run in the background, it also supports scheduling recurring tasks 
+to execute APIs or Commands at fixed intervals.
+
 :::youtube DtB8KaXXMCM
 Schedule your Reoccurring Tasks with Background Jobs!
 :::
 
-APIs and Commands can be scheduled to run at either a `TimeSpan` or 
+APIs and Commands can be scheduled to run at either a `TimeSpan` or
 [CRON Expression](https://github.com/HangfireIO/Cronos?tab=readme-ov-file#cron-format) interval, e.g:
 
 ```csharp
@@ -221,7 +222,7 @@ jobs.RecurringApi(Schedule.Interval(TimeSpan.FromMinutes(1)), new CheckUrls {
 });
 ```
 
-Scheduled Tasks can be registered with an optional task name and custom Background Options, e.g: 
+That can be registered with an optional **Task Name** and **Background Options**, e.g:
 
 ```csharp
 jobs.RecurringCommand<CheckUrlsCommand>("Check URLs", Schedule.EveryMinute, 
@@ -230,14 +231,18 @@ jobs.RecurringCommand<CheckUrlsCommand>("Check URLs", Schedule.EveryMinute,
    });
 ```
 
-If no task name is provided, the Command Name or APIs Request DTO will be used. 
+:::info
+If no name is provided, the Command's Name or APIs Request DTO will be used
+:::
 
-Scheduled Tasks are idempotent where the same registration with the same name will 
+Scheduled Tasks are idempotent where the same registration with the same name will
 either create or update the scheduled task registration without losing track of the
 last time the Recurring Task was run which is also viewable in the Jobs Admin UI:
 
 ![](/img/pages/jobs/jobs-scheduled-tasks-last-job.webp)
 
+As such it's recommended to always define your App's Scheduled Tasks on Startup:
+
 ### Executing non-durable jobs
 
 `IBackgroundJobs` also supports `RunCommand` methods to be able to execute jobs transiently 
@@ -928,10 +933,10 @@ of a singular growing database, visible in the [Database Admin UI](/admin-ui-dat
 SQLite logs will also make it easier to generate monthly aggregate reports to provide key insights
 into the usage of your App.
 
-## Admin Logging UI
+## AutoQuery Grid Admin Logging UI
 
 As SQLite Requests Logs also makes it efficiently possible to sort and filter through logs, the
-Logging UI will switch to using a fully queryable AutoQueryGrid when using `SqliteRequestLogger`:
+Logging UI will switch to using a fully queryable `AutoQueryGrid` when using `SqliteRequestLogger`:
 
 ![](/img/pages/sqlite/sqlite-request-logs.webp)
 
diff --git a/MyApp/_pages/sqlite-request-logs.md b/MyApp/_pages/sqlite-request-logs.md
@@ -92,9 +92,9 @@ of a singular growing database, visible in the [Database Admin UI](/admin-ui-dat
 SQLite logs will also make it easier to generate monthly aggregate reports to provide key insights
 into the usage of your App.
 
-## Admin Logging UI
+## AutoQuery Grid Admin Logging UI
 
 As SQLite Requests Logs also makes it efficiently possible to sort and filter through logs, the
-Logging UI will switch to using a fully queryable AutoQueryGrid when using `SqliteRequestLogger`:
+Logging UI will switch to using a fully queryable `AutoQueryGrid` when using `SqliteRequestLogger`:
 
 ![](/img/pages/sqlite/sqlite-request-logs.webp)
