add detailed instructions (#5767)

## What are you changing in this pull request and why?
Add detailed instructions.

## Checklist

- [ x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ x] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ x] Add a checklist item for anything that needs to happen before
this PR is merged, such as "needs technical review" or "change base
branch."

---------

Co-authored-by: Mirna Wong <[email protected]>

website/docs/guides/mesh-qs.md

@@ -460,10 +460,10 @@ models:
 ### Set up model versions
 In this section, you will set up model versions by the Data Analytics team as they upgrade the `fct_orders` model while offering backward compatibility and a migration notice to the downstream Finance team.
 
-1. Rename the existing model file from` models/core/fct_orders.sql` to `models/core/fct_orders_v1.sql`.
+1. Rename the existing model file from `models/core/fct_orders.sql` to `models/core/fct_orders_v1.sql`.
 2. Create a new file `models/core/fct_orders_v2.sql` and adjust the schema:
-   - Comment out `orders.status`  
-   - Add a new field, `is_return` to indicate if an order was returned.
+   - Comment out `o.status` in the `final` CTE.
+   - Add a new field, `case when o.status = 'returned' then true else false end as is_return` to indicate if an order was returned.
 3. Then, add the following to your `models/core/core.yml` file:
    - The `is_return` column
    - The two model `versions`