Skip to content

Commit 78fbf53

Browse files
committed
Fixed some typos
1 parent b1fc9c9 commit 78fbf53

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/security-center/continuous-export.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ This article describes the set of (preview) tools that allow you to export alert
1818

1919
Using these tools you can:
2020

21-
* Continously export to Log Analytics workspaces
22-
* Continously export to Azure Event Hubs (for integrations with third-party SIEMs)
23-
* Perform a one-time export to CSV
21+
* Continuously export to Log Analytics workspaces
22+
* Continuously export to Azure Event Hubs (for integrations with third-party SIEMs)
23+
* Export to CSV (one time)
2424

2525

2626
## Setting up a continuous export
@@ -46,7 +46,7 @@ The steps below are necessary whether you're setting up a continuous export to L
4646

4747
## Configuring SIEM integration via Azure Event Hubs
4848

49-
Azure Event Hubs is a great solution for programatically consuming any streaming data. In the case of Azure Security Center alerts and recommendations, it's the preferred way to integrate with a third-party SIEM.
49+
Azure Event Hubs is a great solution for programatically consuming any streaming data. For Azure Security Center alerts and recommendations, it's the preferred way to integrate with a third-party SIEM.
5050

5151
> [!NOTE]
5252
> The most effective method to stream monitoring data to external tools in most cases is using Azure Event Hubs. [This article](https://docs.microsoft.com/azure/azure-monitor/platform/stream-monitoring-data-event-hubs) provides a brief description for how you can stream monitoring data from different sources to an Event Hub and links to detailed guidance.

0 commit comments

Comments
 (0)