Skip to content

Commit 709add5

Browse files
committed
minor rewording
1 parent b296609 commit 709add5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/machine-learning/how-to-migrate-from-v1.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You should use v2 if you're starting a new machine learning project or workflow.
3232
* Responsible AI dashboard
3333
* Registry of assets
3434

35-
A new v2 project can reuse existing resources like workspaces and compute and existing assets like models and environments created using v1.
35+
A new v2 project can reuse existing v1 resources like workspaces and compute and existing assets like models and environments created using v1.
3636

3737
Some feature gaps in v2 include:
3838

@@ -211,11 +211,11 @@ A key paradigm with v2 is serializing machine learning entities as YAML files fo
211211

212212
You can obtain a YAML representation of any entity with the CLI via `az ml <entity> show --output yaml`. Note that this output will have system-generated properties, which can be ignored or deleted.
213213

214-
## Should I upgrade existing code to v2
214+
## Should I upgrade existing v1 code to v2
215215

216-
You can reuse your existing assets in your v2 workflows. For instance a model created in v1 can be used to perform Managed Inferencing in v2.
216+
You can reuse your existing v1 assets in your v2 workflows. For instance a model created in v1 can be used to perform Managed Inferencing in v2.
217217

218-
Optionally, if you want to upgrade specific parts of your existing code to v2, please refer to the comparison links provided in the details of each resource or asset in the rest of this document.
218+
Optionally, if you want to upgrade specific parts of your existing v1 code to v2, please refer to the comparison links provided in this document.
219219

220220
## Can I use v1 and v2 together?
221221

0 commit comments

Comments
 (0)