Skip to content

Commit 6cee71f

Browse files
committed
Minor updates
1 parent dbdafb5 commit 6cee71f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/cloud-soar/cloud-soar-end-of-sale.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ At this time we have only announced an end-of-sale of Cloud SOAR as a separate p
6363

6464
#### What will happen when an existing Cloud SOAR license is up for renewal?
6565

66-
Renewals are allowed currently as Cloud SOAR is not under end-of-support or end-of-life. We highly recommend planning a conversion to using the Automation Service already provided within the log management and Cloud SIEM products and discontinuing use of the standalone Cloud SOAR system before the renewal is required.
66+
Renewals are allowed currently as Cloud SOAR is not under end-of-support or end-of-life. We highly recommend planning a transition to the Automation Service already provided within the log management and Cloud SIEM products and discontinuing use of the standalone Cloud SOAR system before the renewal is required.
6767

6868
#### How long will existing Cloud SOAR implementations continue to be supported?
6969

@@ -121,7 +121,7 @@ The Automation Service is included in our core platform offerings. However, you
121121

122122
#### Will my current third-party integrations continue to work?
123123

124-
Yes, the Automation Service support the same integrations as Cloud SOAR. Your existing third-party tool connections and APIs will continue to function after migration.
124+
Yes, the Automation Service supports the same integrations as Cloud SOAR. Your existing third-party tool connections and APIs will continue to function after migration.
125125

126126
#### What happens to my historical data and case information?
127127

0 commit comments

Comments
 (0)