Merge pull request #293961 from Ankit-MSFT/docs-editor/concepts-event-grid-namespaces-1738491568

Update concepts-event-grid-namespaces.md

Author: prmerger-automator[bot]

articles/event-grid/concepts-event-grid-namespaces.md

@@ -13,7 +13,7 @@ ms.topic: concept-article
 This article introduces you to the main concepts and functionality associated to namespace topics.
 
 ## Events
-An **event** is the smallest amount of information that fully describes something that happened in a system. We often refer to an event as a discrete event because it represents a distinct, self-standing fact about a system that provides an insight that can be actionable. Every event has common information like `source` of the event, `time` the event took place, and a unique identifier. Event every also has a `type`, which usually is a unique identifier that describes the kind of announcement the event is used for. 
+An **event** is the smallest amount of information that fully describes something that happened in a system. We often refer to an event as a discrete event because it represents a distinct, self-standing fact about a system that provides an insight that can be actionable. Every event has common information like `source` of the event, `time` the event took place, and a unique identifier. Every event also has a `type`, which usually is a unique identifier that describes the kind of announcement the event is used for. 
 
 For example, an event about a new file being created in Azure Storage has details about the file, such as the `lastTimeModified` value. An Event Hubs event has the URL of the captured file. An event about a new order in your Orders microservice might have an `orderId` attribute and a URL attribute to the order’s state representation. A few more examples of event types include: `com.yourcompany.Orders.OrderCreated`, `org.yourorg.GeneralLedger.AccountChanged`, `io.solutionname.Auth.MaximumNumberOfUserLoginAttemptsReached`.