Skip to content

Commit cba9a0e

Browse files
authored
docs: minor fixes to v1 sunset docs (coder#1196)
1 parent 81e44b0 commit cba9a0e

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

guides/v2-faq.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Coder v1 will have 3 sunset or end-of-life dates.
2525
<details>
2626
<summary>How will we continue to get v1 support?</summary>
2727

28-
Yes. Continue to either work with your account executive at Coder or leverage
28+
Continue to either coordinate with your Coder account executive or leverage
2929
the [Slack](https://cdr.co/join-community) channel.
3030

3131
</details>
@@ -39,16 +39,16 @@ make workspace compute a Kubernetes pod, a VM, or a Docker container, and an
3939
open-source platform for the community to get the developer-centric benefits of
4040
remote development without a license fee. See the blog post [Lessons learned
4141
from
42-
v1](https://coder.com/blog/lessons-learned-from-v1-and-oss-to-enterprise-editions)
42+
v1](https://coder.com/blog/lessons-learned-from-v1-and-oss-to-enterprise-editions).
4343

4444
</details>
4545

4646
<details>
4747
<summary>What Coder v2 features are open-source and paid?</summary>
4848

49-
Functionality for a developer to be productive are in the open-source, while
49+
Functionality for a developer to be productive are in the v2 OSS, while
5050
scalability, governance and control features for DevOps teams are in the
51-
Enterprise paid version. [See this page for feature
51+
v2 Enterprise paid version. [See this page for feature
5252
comparisons.](https://coder.com/pricing)
5353

5454
</details>
@@ -75,23 +75,23 @@ platform into a new code base. v2 also has a different Postgres database schema.
7575

7676
In v1, workspaces are Kubernetes pods with an inner container based on [container
7777
images](../images/index.md) with an optional configure script in the image that runs additional
78-
configurations as the non-root user after the workspace is built. v1 has an
78+
configurations as the non-root user after the workspace is built. Coder v1 has an
7979
optional workspace template yaml spec to define compute and additional bash
8080
scripting steps.
8181

82-
In v2, workspaces are defined as [Terraform
82+
In Coder v2, workspaces are defined as [Terraform
8383
templates](https://coder.com/docs/coder-oss/latest/templates) with Terraform
84-
resources to define the compute type. e.g., Kubernetes pod, Docker container, or
85-
VM. Docker or alternatively VM images are specified in the template. The
86-
template includes a `startup_script` configuration that can run the configure
87-
script in the image or additional steps like in v1 workspace templates. v1
88-
workspace applications are configured as `coder_app` resources in the Terraform
89-
template.
84+
resources to specify the infrastructure provider and compute type. e.g.,
85+
Kubernetes pod, Docker container, or VM. Docker or alternatively VM images are
86+
specified in the template. The template includes an agent resource and
87+
`startup_script` configuration that can run the configure script in the image or
88+
additional steps like in v1 workspace templates. Coder v1 workspace applications
89+
are configured as `coder_app` resources in the Terraform template.
9090

9191
v1 [organizations](../admin/organizations/index.md) are
9292
[groups](https://coder.com/docs/coder-oss/latest/admin/groups) in v2.
9393

94-
Integration points remain like
94+
Integration points remain the same like
9595
[OIDC](https://coder.com/docs/coder-oss/latest/admin/auth) for single-sign-on
9696
and specifying image registries in v2 templates.
9797

@@ -108,7 +108,7 @@ is preferred.
108108
<summary>Are there migration scripts from v1 to v2?</summary>
109109

110110
No. The database schema and architectural concepts are so different in v2, it is
111-
not reasonable to build migration scripts that meet customer deployment
111+
not reasonable to build migration scripts that meet all customer deployment
112112
scenarios. See [the migration strategy](./moving-to-oss.md#migration-strategy)
113113
and [recommendations on moving workspace
114114
contents](./moving-to-oss.md#workspaces).
@@ -128,6 +128,6 @@ community.
128128

129129
</br>
130130

131-
> For more information on v2 concepts, please review the [Moving to Coder
131+
> For more information on Coder v2 concepts, please review the [Moving to Coder
132132
> v2](./moving-to-oss.md) guide.
133133

0 commit comments

Comments
 (0)