Skip to content

Commit 3db2787

Browse files
Sanmeeta23sanmeeta.raj
andauthored
Documentation update to remove the unwanted html tag (#574)
* #MMS-3804 : Bug Fix * #MMS-3804 : Bug Fix --------- Co-authored-by: sanmeeta.raj <sanmeeta.raj@imperva.com>
1 parent 4e21bdc commit 3db2787

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

website/docs/r/notification_center_policy.html.markdown

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -91,14 +91,9 @@ The following arguments are supported:
9191
We recommend always setting this field's value to `FALSE`, to disable automatic updates of sub-accounts on the policy,
9292
so you have full control over your resources.
9393

94-
95-
<<<<<<< HEAD:website/docs/r/notification_policy.html.markdown
96-
Under the following conditions, you need to define at least 1 asset:\
97-
If the `policy_type` argument is `ACCOUNT`, and the selected `sub_category` requires that the policy be applied to assets in the account, and the
98-
=======
94+
9995
Under the following conditions, you need to define at least 1 asset:
100-
If the `policy_type` argument is `ACCOUNT`, and the chosen `sub_category` requires configuration of assets, and the
101-
>>>>>>> docs-update:website/docs/r/notification_center_policy.html.markdown
96+
If the `policy_type` argument is `ACCOUNT`, and the chosen `sub_category` requires configuration of assets, and the
10297
argument `apply_to_new_assets` is `FALSE`, then at least 1 asset must be defined.\
10398
For example, when configuring a policy for the `SITE_NOTIFICATIONS` `sub_category`, if the argument `apply_to_new_assets` is FALSE, at least one SITE asset must be specified.
10499
The arguments that are supported in `asset` sub resource are:

0 commit comments

Comments
 (0)