Skip to content

Commit f5150cd

Browse files
authored
Update how-to-manage-models-mlflow.md
1 parent 35aea3d commit f5150cd

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/machine-learning/how-to-manage-models-mlflow.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ ms.custom: how-to, devx-track-python
1515

1616
# Manage models registries in Azure Machine Learning with MLflow
1717

18-
Azure Machine Learning supports MLflow for model management. This represents a convenient way to support the entire model lifecycle for users familiar with the MLFlow client. The following article describes the different capabilities and how it compares with other options.
18+
Azure Machine Learning supports MLflow for model management. Such approach represents a convenient way to support the entire model lifecycle for users familiar with the MLFlow client. The following article describes the different capabilities and how it compares with other options.
1919

2020
### Prerequisites
2121

2222
[!INCLUDE [mlflow-prereqs](../../includes/machine-learning-mlflow-prereqs.md)]
2323

24-
* Some operations may be executed directly using the MLflow fluent API (`mlflow.<method>`). However, others may require to create an MLflow client, which allows to communicate with Azure Machine Learning in the MLflow protocol. You can create an `MlflowClient` object as follows. This tutorial will use the object `client` to refer to such MLflow client.
24+
* Some operations may be executed directly using the MLflow fluent API (`mlflow.<method>`). However, others may require to create an MLflow client, which allows to communicate with Azure Machine Learning in the MLflow protocol. You can create an `MlflowClient` object as follows. This tutorial uses the object `client` to refer to such MLflow client.
2525

2626
```python
2727
using mlflow
@@ -35,7 +35,7 @@ The models registry offer a convenient and centralized way to manage models in a
3535

3636
### Creating models from an existing run
3737

38-
If you have an MLflow model logged inside of a run and you want to register it in a registry, you can do that by using the run ID and the path where the model was logged. See [Manage experiments and runs with MLflow](how-to-track-experiments-mlflow.md) to know how to query this information if you don't have it.
38+
If you have an MLflow model logged inside of a run and you want to register it in a registry, use the run ID and the path where the model was logged. See [Manage experiments and runs with MLflow](how-to-track-experiments-mlflow.md) to know how to query this information if you don't have it.
3939

4040
```python
4141
mlflow.register_model(f"runs:/{run_id}/{artifact_path}", model_name)
@@ -96,7 +96,7 @@ client.search_registered_models(order_by=["name ASC"])
9696
9797
### Getting specific versions of the model
9898

99-
The command above will retrieve the model object which contains all the model versions. However, if you want to get the last registered model version of a given model, you can use `get_registered_model`:
99+
The `search_registered_models()` command retrieves the model object, which contains all the model versions. However, if you want to get the last registered model version of a given model, you can use `get_registered_model`:
100100

101101
```python
102102
client.get_registered_model(model_name)
@@ -154,7 +154,7 @@ Transitioning a model's version to a particular stage can be done using the MLfl
154154
client.transition_model_version_stage(model_name, version=3, stage="Staging")
155155
```
156156

157-
By default, if there were an existing model version in that particular stage, it will remain there. Hence, it won't be replaced as multiple model's versions can be in the same stage at the same time. Alternatively, you can indicate `archive_existing_versions=True` to tell MLflow to move the existing model's version to the stage `Archived`.
157+
By default, if there were an existing model version in that particular stage, it remains there. Hence, it isn't replaced as multiple model's versions can be in the same stage at the same time. Alternatively, you can indicate `archive_existing_versions=True` to tell MLflow to move the existing model's version to the stage `Archived`.
158158

159159
```python
160160
client.transition_model_version_stage(

0 commit comments

Comments
 (0)