Update 3.3.0-BETA everywhere

heyams · heyams · commit 3bdd3ed94841 · 2022-06-22T09:26:22.000-07:00
diff --git a/articles/azure-monitor/app/java-in-process-agent.md b/articles/azure-monitor/app/java-in-process-agent.md
@@ -33,9 +33,9 @@ Download the [applicationinsights-agent-3.3.0.jar](https://github.com/microsoft/
 
 > [!WARNING]
 > 
-> If you're upgrading from 3.2.x to 3.3.0-BETA:
+> If you're upgrading from 3.2.x to 3.3.0:
 > 
->    -  Starting from 3.3.0-BETA, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is already captured in the `SeverityLevel` field. For details on how to re-enable this if needed, please see the [config options](./java-standalone-config.md#logginglevel)
+>    -  Starting from 3.3.0, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is already captured in the `SeverityLevel` field. For details on how to re-enable this if needed, please see the [config options](./java-standalone-config.md#logginglevel)
 >
 > If you're upgrading from 3.1.x:
 > 
diff --git a/articles/azure-monitor/app/java-standalone-config.md b/articles/azure-monitor/app/java-standalone-config.md
@@ -319,7 +319,7 @@ These are the valid `level` values that you can specify in the `applicationinsig
 
 ### LoggingLevel
 
-Starting from version 3.3.0-BETA, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is aleady captured in the `SeverityLevel` field. 
+Starting from version 3.3.0, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is aleady captured in the `SeverityLevel` field. 
 
 If needed, you can re-enable the previous behavior:
 

Original file line number	Diff line number	Diff line change
`@@ -33,9 +33,9 @@ Download the [applicationinsights-agent-3.3.0.jar](https://github.com/microsoft/`
`33`	`33`
`34`	`34`	`> [!WARNING]`
`35`	`35`	`>`
`36`		`-> If you're upgrading from 3.2.x to 3.3.0-BETA:`
	`36`	`+> If you're upgrading from 3.2.x to 3.3.0:`
`37`	`37`	`>`
`38`		-> - Starting from 3.3.0-BETA, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is already captured in the `SeverityLevel` field. For details on how to re-enable this if needed, please see the [config options](./java-standalone-config.md#logginglevel)
	`38`	+> - Starting from 3.3.0, `LoggingLevel` is not captured by default as part of Traces' custom dimension since that data is already captured in the `SeverityLevel` field. For details on how to re-enable this if needed, please see the [config options](./java-standalone-config.md#logginglevel)
`39`	`39`	`>`
`40`	`40`	`> If you're upgrading from 3.1.x:`
`41`	`41`	`>`