Update documentation for cron change (#3194)

* initial commit

* run prettier

* change to office hours link

* fix lint :/

Author: juliusgeo

frontend/docs/pages/v1/cron-runs.mdx

@@ -29,15 +29,18 @@ Hatchet supports cron triggers to run on a schedule defined in a few different w
 
 ### Cron Expression Syntax
 
-Cron expressions in Hatchet follow the standard cron syntax. A cron expression consists of five fields separated by spaces:
+Cron expressions in Hatchet follow the standard cron syntax. Hatchet supports both 5-field and 6-field expressions.
+A cron expression consists 5 to 6 fields separated by spaces. If there are 6 fields, the first field is seconds; if
+there are 5 fields, the first field is minutes.
 
 ```
-┌───────────── minute (0 - 59)
-│ ┌───────────── hour (0 - 23)
-│ │ ┌───────────── day of the month (1 - 31)
-│ │ │ ┌───────────── month (1 - 12)
-│ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday)
-* * * * *
+┌───────────── second (0 - 59) (optional)
+| ┌───────────── minute (0 - 59)
+│ │ ┌───────────── hour (0 - 23)
+│ │ │ ┌───────────── day of the month (1 - 31)
+│ │ │ │ ┌───────────── month (1 - 12)
+│ │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday)
+* * * * * *
 ```
 
 Each field can contain a specific value, an asterisk (`*`) to represent all possible values, or a range of values. Here are some examples of cron expressions:
@@ -46,6 +49,12 @@ Each field can contain a specific value, an asterisk (`*`) to represent all poss
 - `*/15 * * * *`: Run every 15 minutes
 - `0 9 * * 1`: Run every Monday at 9 AM
 - `0 0 1 * *`: Run on the first day of every month at midnight
+- `30 * * * * *`: Run at 30 seconds past every minute (6-field)
+
+<Callout type="info">
+  Keep in mind, Hatchet Cloud meters by Task runs so use seconds wisely. Have
+  questions about pricing? [Contact us](https://hatchet.run/office-hours)
+</Callout>
 
 ## Defining a Cron in Your Task Definition