Skip to content

Commit 3f96ffb

Browse files
committed
minor fixes
1 parent 9330b46 commit 3f96ffb

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/cognitive-services/language-service/concepts/model-lifecycle.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -64,14 +64,14 @@ Use the table below to find which model versions are supported by each feature:
6464

6565
As new training configs and new functionality become available; older and less accurate configs are retired, see the following timelines for configs expiration:
6666

67-
New configs are being released every few months. So, training configs expiration of any publicly available config is **six months** after its release. If you have assigned a trained model to a deployment, this deployment expires after **twelve months** from the training config expiration. If your models are about to expire, you can retrain and redeploy your models with the latest training configuration version.
67+
New configs are being released every few months. So, training configs expiration of any publicly available config is **six months** after its release. If you've assigned a trained model to a deployment, this deployment expires after **twelve months** from the training config expiration. If your models are about to expire, you can retrain and redeploy your models with the latest training configuration version.
6868

69-
After training config version expires, API calls will return an error when called or used if called with an expired config version. By default, training requests will use the latest available training config version. To change the config version, use `trainingConfigVersion` when submitting a training job and assign the version you want.
69+
After training config version expires, API calls will return an error when called or used if called with an expired config version. By default, training requests use the latest available training config version. To change the config version, use `trainingConfigVersion` when submitting a training job and assign the version you want.
7070

7171
> [!Tip]
7272
> It's recommended to use the latest supported config version
7373
74-
You can train and deploy a custom AI model from the date of training config version release, up until the **Training config expiration** date. After this date, you will have to use another supported training config version for submitting any training or deployment jobs.
74+
You can train and deploy a custom AI model from the date of training config version release, up until the **Training config expiration** date. After this date, you'll have to use another supported training config version for submitting any training or deployment jobs.
7575

7676
Deployment expiration is when your deployed model will be unavailable to be used for prediction.
7777

@@ -90,9 +90,9 @@ Use the table below to find which model versions are supported by each feature:
9090

9191
When you're making API calls to the following features, you need to specify the `API-VERISON` you want to use to complete your request. It's recommended to use the latest available API versions.
9292

93-
If you're using the [Language Studio](https://aka.ms/languageStudio) for building your project you will be using the latest API version available. If you need to use another API version this is only available directly through APIs.
93+
If you're using [Language Studio](https://aka.ms/languageStudio) for your projects, you'll use the latest API version available. Other API versions are only available through the REST APIs and client libraries.
9494

95-
Use the table below to find which API versions are supported by each feature:
95+
Use the following table to find which API versions are supported by each feature:
9696

9797
| Feature | Supported versions | Latest Generally Available version | Latest preview version |
9898
|-----------------------------------------------------|---------------------------------------------------------------------|------------------------------------|------------------------|

0 commit comments

Comments
 (0)