Skip to content

Commit 21c6283

Browse files
authored
Update how-to-deploy-models-timegen-1.md
1 parent fdce1f0 commit 21c6283

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/how-to-deploy-models-timegen-1.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,11 +100,11 @@ These steps demonstrate the deployment of TimeGEN-1. To create a deployment:
100100
1. Once you subscribe the workspace for the particular Azure Marketplace offering, subsequent deployments of the _same_ offering in the _same_ workspace don't require subscribing again. If this scenario applies to you, you'll see a **Continue to deploy** option to select.
101101
1. Give the deployment a name. This name becomes part of the deployment API URL. This URL must be unique in each Azure region.
102102
1. Select **Deploy**. Wait until the deployment is ready and you're redirected to the Deployments page.
103-
1. Take note of the **Target URI** and the secret **Key**, which you can use to call the deployment and generate completions. For more information on using the APIs, see the [reference](#reference-for-timegen-1-deployed-as-a-serverless-api) section.
103+
1. Take note of the **Target URI** and the secret **Key**, which you can use to call the deployment and generate completions. For more information on using the APIs, see the [reference](#reference-for-timegen-1-deployed-as-a-standard-deployment) section.
104104
1. Select the **Test** tab to start interacting with the model.
105105
1. You can always find the endpoint's details, URI, and access keys by navigating to **Workspace** > **Endpoints** > **Serverless endpoints**.
106106

107-
To learn about billing for the TimeGEN-1 model deployed as a standard deployment with pay per token offer billing, see [Cost and quota considerations for TimeGEN-1 deployed as a standard deployment](#cost-and-quota-considerations-for-timegen-1-deployed-as-a-serverless-api).
107+
To learn about billing for the TimeGEN-1 model deployed as a standard deployment with pay per token offer billing, see [Cost and quota considerations for TimeGEN-1 deployed as a standard deployment](#cost-and-quota-considerations-for-timegen-1-deployed-as-a-standard-deployment).
108108

109109
### Consume the TimeGEN-1 model as a service
110110

@@ -126,7 +126,7 @@ You can consume TimeGEN-1 models by using the forecast API.
126126
|Exogenous Variables|Exogenous variables are external factors that can influence forecasts. These variables take on one of a limited, fixed number of possible values, and induce a grouping of your observations. For example, if you're forecasting daily product demand for a retailer, you could benefit from an event variable that may tell you what kind of event takes place on a given day, for example 'None', Sporting', or 'Cultural'. Or you might also include external factors such as weather.|[Exogenous Variables](https://aka.ms/exogenous-variables)|
127127
|Demand Forecasting|Demand forecasting involves application of historical data and other analytical information, to build models that help predict future estimates of customer demand, for specific products, over a specific time period. It helps shape product road map, inventory production, and inventory allocation, among other things.|[Demand Forecasting](https://aka.ms/demand-forecasting-with-TimeGEN1)|
128128

129-
For more information about use of the APIs, visit the [Reference](#reference-for-timegen-1-deployed-as-a-serverless-api) section.
129+
For more information about use of the APIs, visit the [Reference](#reference-for-timegen-1-deployed-as-a-standard-deployment) section.
130130

131131
### Reference for TimeGEN-1 deployed as a standard deployment
132132

0 commit comments

Comments
 (0)