SUMO-253872: Fix copy/paste errors

Author: ShahzaibA123

CHANGELOG.md

@@ -1,7 +1,6 @@
 ## X.Y.Z (Unreleased)
 * Add new change notes here
 
-## 3.0.5 (February 28, 2025)
 ENHANCEMENTS:
 * Add support for monitor frequency configurability
 

website/docs/r/monitor.html.markdown

@@ -534,14 +534,14 @@ Here is a summary of arguments for each condition type (fields which are not mar
   - `field`
   - `critical`
     - `time_range` (Required) : Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
-    - `frequency` Accepted format: Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `1m`, `2m`, `10m`'.
+    - `frequency` Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `1m`, `2m`, `10m`'.
     - `alert` (Required)
       - `threshold`
       - `threshold_type`
     - `resolution` (Required)
       - `threshold`
       - `threshold_type`
-      - `resolution_window` pted format: `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `0s, 30m`.
+      - `resolution_window` Accepted format: `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `0s, 30m`.
   - `warning`
     - `time_range` (Required) :  Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
     - `alert` (Required)
@@ -558,7 +558,7 @@ Here is a summary of arguments for each condition type (fields which are not mar
     - `alert` (Required)
       - `threshold`
       - `threshold_type`
-      - `min_data_points` (OptionalAcce)
+      - `min_data_points` (Optional)
     - `resolution` (Required)
       - `threshold`
       - `threshold_type`
@@ -595,7 +595,6 @@ Here is a summary of arguments for each condition type (fields which are not mar
     - `threshold`
 #### logs_missing_data_condition
   - `time_range` (Required) :  Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
-  - `frequency` Accepted format: Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `1m`, `2m`, `10m`'.
 #### metrics_missing_data_condition
   - `time_range` (Required) :  Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
 #### slo_sli_condition