Update reference-yaml-component-command.md

Author: JasonWHowell

articles/machine-learning/reference-yaml-component-command.md

@@ -37,7 +37,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
 | `is_deterministic` | boolean |This option determines if the component will produce the same output for the same input data. You should usually set this to `false` for components that load data from external sources, such as importing data from a URL. This is because the data at the URL might change over time. | | `true` |
 | `command` | string | **Required.** The command to execute. | | |
 | `code` | string | Local path to the source code directory to be uploaded and used for the component. | | |
-| `environment` | string or object | **Required.** The environment to use for the component. This value can be either a reference to an existing versioned environment in the workspace or an inline environment specification. <br><br> To reference an existing custom environment, use the `azureml:<environment-name>:<environment-version>` syntax. To reference a curated environment, use the `azureml://registries/azureml/environment/<curated-environment-name>/versions/<version-number>` syntax. For more information on how to reference environments see [How to Manage Environments](machine-learning/how-to-manage-environments-v2.md) <br><br> To define an environment inline, follow the [Environment schema](reference-yaml-environment.md#yaml-syntax). Exclude the `name` and `version` properties as they aren't supported for inline environments. | | |
+| `environment` | string or object | **Required.** The environment to use for the component. This value can be either a reference to an existing versioned environment in the workspace or an inline environment specification. <br><br> To reference an existing custom environment, use the `azureml:<environment-name>:<environment-version>` syntax. To reference a curated environment, use the `azureml://registries/azureml/environment/<curated-environment-name>/versions/<version-number>` syntax. For more information on how to reference environments see [How to Manage Environments](how-to-manage-environments-v2.md) <br><br> To define an environment inline, follow the [Environment schema](reference-yaml-environment.md#yaml-syntax). Exclude the `name` and `version` properties as they aren't supported for inline environments. | | |
 | `distribution` | object | The distribution configuration for distributed training scenarios. One of [MpiConfiguration](#mpiconfiguration), [PyTorchConfiguration](#pytorchconfiguration), or [TensorFlowConfiguration](#tensorflowconfiguration). | | |
 | `resources.instance_count` | integer | The number of nodes to use for the job. | | `1` |
 | `inputs` | object | Dictionary of component inputs. The key is a name for the input within the context of the component and the value is the component input definition. <br><br> Inputs can be referenced in the `command` using the `${{ inputs.<input_name> }}` expression. | | |