Merge branch 'current' into patch-1

website/docs/docs/core/docker-install.md

@@ -30,11 +30,23 @@ docker pull ghcr.io/dbt-labs/<db_adapter_name>:<version_tag>
 ### Running a dbt Docker image in a container
 
 The `ENTRYPOINT` for dbt Docker images is the command `dbt`. You can bind-mount your project to `/usr/app` and use dbt as normal:
+
+```
+docker run \
+--network=host \
+--mount type=bind,source=path/to/project,target=/usr/app \
+--mount type=bind,source=path/to/profiles.yml,target=/root/.dbt/profiles.yml \
+<dbt_image_name> \
+ls
+```
+
+Or 
+
 ```
 docker run \
 --network=host \
 --mount type=bind,source=path/to/project,target=/usr/app \
---mount type=bind,source=path/to/profiles.yml,target=/root/.dbt/ \
+--mount type=bind,source=path/to/profiles.yml.dbt,target=/root/.dbt/ \
 <dbt_image_name> \
 ls
 ```

website/docs/docs/deploy/job-scheduler.md

@@ -11,9 +11,10 @@ The job scheduler is the backbone of running jobs in dbt Cloud, bringing power a
 The scheduler enables both cron-based and event-driven execution of dbt commands in the user’s data platform. Specifically, it handles:
 
 - Cron-based execution of dbt Cloud jobs that run on a predetermined cadence
-- Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo
+- Event-driven execution of dbt Cloud jobs that run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion))
+- Event-driven execution of dbt Cloud CI jobs triggered when a pull request is merged to the branch ([merge jobs](/docs/deploy/merge-jobs))
 - Event-driven execution of dbt Cloud jobs triggered by API
-- Event-driven execution of dbt Cloud jobs manually triggered by a user to "Run Now"
+- Event-driven execution of dbt Cloud jobs manually triggered by a user to **Run now**
 
 The scheduler handles various tasks including queuing jobs, creating temporary environments to run the dbt commands required for those jobs, providing logs for debugging and remediation, and storing dbt artifacts for direct consumption/ingestion by the Discovery API. 
 

website/docs/guides/redshift-qs.md

@@ -118,8 +118,7 @@ Now we are going to load our sample data into the S3 bucket that our Cloudformat
         id integer,
         user_id integer,
         order_date date,
-        status varchar(50),
-        _etl_loaded_at timestamp default current_timestamp
+        status varchar(50)
     );
 
     create table stripe.payment(
@@ -128,8 +127,7 @@ Now we are going to load our sample data into the S3 bucket that our Cloudformat
         paymentmethod varchar(50),
         status varchar(50),
         amount integer,
-        created date,
-        _batched_at timestamp default current_timestamp
+        created date
     );
     ```