Merge pull request #947 from cjgajard/alert-grouping-setting-migratio…

…n-msg

Add link to migration docs in alert_grouping_parameters deprecation

pagerduty/resource_pagerduty_service.go

@@ -78,7 +78,7 @@ func resourcePagerDutyService() *schema.Resource {
 				Optional:      true,
 				Computed:      true,
 				MaxItems:      1,
-				Deprecated:    "Use a resource `pagerduty_alert_grouping_setting` instead",
+				Deprecated:    "Use a resource `pagerduty_alert_grouping_setting` instead.\nFollow the migration guide at https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/alert_grouping_setting#migration-from-alert_grouping_parameters",
 				ConflictsWith: []string{"alert_grouping", "alert_grouping_timeout"},
 				Elem: &schema.Resource{
 					Schema: map[string]*schema.Schema{

website/docs/r/slack_connection.html.markdown

@@ -80,9 +80,9 @@ The following arguments are supported:
     - `incident.status_update_published`
     - `incident.reopened`
   * `priorities` - (Optional) Allows you to filter events by priority. Needs to be an array of PagerDuty priority IDs. Available through [pagerduty_priority](https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/data-sources/priority) data source.
-    - When omitted or set to an empty array (`[]`) in the configuration for a Slack Connection, its default behaviour is to set `priorities` to `No Priority` value.
+    - When omitted or set to an empty array (`[]`) in the configuration for a Slack Connection, its default behavior is to set `priorities` to `No Priority` value.
     - When set to `["*"]` its corresponding value for `priorities` in Slack Connection's configuration will be `Any Priority`.
-  * `urgency` - (Optional) Allows you to filter events by urgency. Either `high` or `low`.
+  * `urgency` - (Optional) Allows you to filter events by urgency. Either `high`, `low` or `null` for Any urgency. Default is `null`.
 
 ## Attributes Reference