Changes to the note as suggested by PG

Author: kpeechara

articles/azure-monitor/containers/container-insights-logs-schema.md

@@ -62,7 +62,7 @@ You can enable the **ContainerLogV2** schema for a cluster either using the clus
 With multiline logging enabled, previously split container logs are stitched together and sent as single entries to the ContainerLogV2 table. If the stitched log line is larger than 64 KB, it will be truncated due to Log Analytics workspace limits. This feature also has support for .NET, Go, Python and Java stack traces, which appear as single entries in the ContainerLogV2 table. Enable multiline logging with ConfigMap as described in [Configure data collection in Container insights using ConfigMap](container-insights-data-collection-configmap.md).
 
 >[!NOTE]
-> The configmap now features a language specification option, wherein the customers are required to include their preferred languages. This feature can be enable by editing the languages in the [configmap](https://github.com/microsoft/Docker-Provider/blob/ci_prod/kubernetes/container-azm-ms-agentconfig.yaml#L50).
+> The configmap now features a language specification option, wherein the customers can select only the languages that they are interested in. This feature can be enabled by editing the languages in the stacktrace_languages option in the [configmap](https://github.com/microsoft/Docker-Provider/blob/ci_prod/kubernetes/container-azm-ms-agentconfig.yaml).
 
 The following screenshots show multi-line logging for Go exception stack trace: