Docs: Update backfill image and other fixes

site/docs/guides/customize-dataflows/materialization-sync-schedule.md

@@ -17,12 +17,8 @@ reduce the costs incurred in the destination from the actions the connector
 takes to load data to it.
 :::
 
-These materialization connectors support configuring a sync schedule:
-- [materialize-bigquery](/reference/Connectors/materialization-connectors/BigQuery)
-- [materialize-databricks](/reference/Connectors/materialization-connectors/databricks)
-- [materialize-motherduck](/reference/Connectors/materialization-connectors/motherduck)
-- [materialize-redshift](/reference/Connectors/materialization-connectors/amazon-redshift)
-- [materialize-snowflake](/reference/Connectors/materialization-connectors/Snowflake)
+Most warehouse materialization connectors (such as [Snowflake](/reference/Connectors/materialization-connectors/Snowflake), [Databricks](/reference/Connectors/materialization-connectors/databricks), and [BigQuery](/reference/Connectors/materialization-connectors/BigQuery)) support configuring a sync schedule.
+Check the connector reference docs to determine if a specific connector supports sync schedules.
 
 ## How transactions are used to sync data to a destination
 
@@ -65,6 +61,28 @@ schedule:
 | `/fastSyncStopTime`    | Fast Sync Stop Time    | Time of day that transactions stop executing at the configured Sync Frequency. After this time transactions will be executed more slowly. Must be in the form of '17:00'.                                                                                                                                                                                                     | string |
 | `/fastSyncEnabledDays` | Fast Sync Enabled Days | Days of the week that the configured Sync Frequency is active. On days that are not enabled, transactions will be executed more slowly for the entire day. Examples: 'M-F' (Monday through Friday, inclusive), 'M,W,F' (Monday, Wednesday, and Friday), 'Su-T,Th-S' (Sunday through Tuesday, inclusive; Thursday through Saturday, inclusive). All days are enabled if unset. | string |
 
+The sync schedule can be configured in the dashboard or directly in the materialization's specification file.
+Sync schedule properties are nested under a materialization's `config` stanza. For example:
+
+```yaml
+materializations:
+  your-org/mat-name/materialize-snowflake:
+    endpoint:
+      connector:
+        image: ghcr.io/estuary/materialize-snowflake:v4
+        config:
+          host: orgname-accountname.snowflakecomputing.com
+          database: estuary_db
+          credentials:
+            {...}
+          syncSchedule:
+            fastSyncEnabledDays: M-F
+            fastSyncStartTime: 06:00
+            fastSyncStopTime: 18:00
+            syncFrequency: 30m
+            timezone: EST
+```
+
 :::warning
 Changes to a [materialization's
 specification](/concepts/materialization/#specification) are only applied

site/docs/guides/flowctl/ci-cd.md

@@ -57,7 +57,7 @@ captures:
   Artificial-Industries/ci-cd/source-stripe-native:
     endpoint:
       connector:
-        image: ghcr.io/estuary/source-stripe-native:dev
+        image: ghcr.io/estuary/source-stripe-native:v1
         config:
           credentials:
             credentials_title: Private App Credentials
@@ -82,7 +82,7 @@ captures:
   Artificial-Industries/ci-cd/source-postgres:
     endpoint:
       connector:
-        image: ghcr.io/estuary/source-postgres:dev
+        image: ghcr.io/estuary/source-postgres:v3
         config:
           address: <host>:<port>
           database: postgres
@@ -314,9 +314,9 @@ Consider this example specification:
 materializations:
   Artificial-Industries/ci-cd/materialize-snowflake:
     endpoint:
-  	  connector:
-        image: ghcr.io/estuary/materialize-snowflake:dev
-    	config:
+      connector:
+        image: ghcr.io/estuary/materialize-snowflake:v4
+        config:
           host: orgname-accountname.snowflakecomputing.com
           database: estuary_db
           schema: estuary_schema

site/docs/reference/Connectors/capture-connectors/HubSpot.md

@@ -1,9 +1,11 @@
 
-# HubSpot
+# HubSpot (Deprecated)
 
 This connector captures data from a Hubspot account.
 
-Estuary offers a in-house real time version of this connector. For more information take a look at our [HubSpot Real-Time](/reference/Connectors/capture-connectors/HubSpot-real-time.md) docs.
+:::warning
+This connector is deprecated. It is recommended that you use the new native [HubSpot connector](/reference/Connectors/capture-connectors/HubSpot-real-time) instead.
+:::
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/calendly.md

@@ -2,9 +2,6 @@
 
 This connector captures data from Calendly into Estuary collections.
 
-This connector is available for use in the Estuary web application.
-For local development or open-source workflows, [`ghcr.io/estuary/source-calendly:v1`](https://ghcr.io/estuary/source-calendly:v1) provides the latest connector image. You can also follow the link in your browser to see past image versions.
-
 ## Supported data resources
 
 The connector captures the following Calendly resources: