fixed warning

Author: spelluru

articles/event-hubs/dot-net-development.md

@@ -239,8 +239,3 @@ See the following samples (in the order of complexity).
 - [Capturing Event Hubs logs using AzureEventSourceListener class](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/eventhub/Azure.Messaging.EventHubs/samples/Sample10_AzureEventSourceListener.md)  
   A demonstration of how to use the [`AzureEventSourceListener`](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/Azure.Core/samples/Diagnostics.md#logging) from the `Azure.Core` package to capture logs emitted by the Event Hubs client library.
 
-## Next steps
-See the following quickstarts and samples. 
-
-- Quickstarts: [.NET](event-hubs-dotnet-standard-getstarted-send.md), [Java](event-hubs-java-get-started-send.md), [Python](event-hubs-python-get-started-send.md), [JavaScript](event-hubs-node-get-started-send.md)
-- Samples on GitHub: [.NET](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/eventhub/Azure.Messaging.EventHubs/samples), [Java](https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/eventhubs/azure-messaging-eventhubs/src/samples), [Python](https://github.com/Azure/azure-sdk-for-python/blob/azure-eventhub_5.3.1/sdk/eventhub/azure-eventhub/samples), [JavaScript](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventhub/event-hubs/samples/v5/javascript), [TypeScript](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventhub/event-hubs/samples/v5/typescript)

articles/event-hubs/hello-world-publish-receive-events.md

@@ -79,7 +79,7 @@ A consumer is associated with a specific event hub and [consumer group](event-hu
 
 Each consumer has a unique view of the events in a partition that it reads from, which means that events are available to all consumers and aren't removed from the partition when read. It allows consumers to read and process events from the event hub at different speeds without interfering with one another.
 
-When events are published, they'll continue to exist in the event hub. They'll be available for consuming until they reach an age where they're older than the [retention period](event-hubs-faq.md#what-is-the-maximum-retention-period-for-events). Once removed, the events are no longer available to be read, and can't be recovered. Though the Event Hubs service is free to remove events older than the retention period, it doesn't do so deterministically. There's no guarantee of when events will be removed.
+When events are published, they'll continue to exist in the event hub. They'll be available for consuming until they reach an age where they're older than the [retention period](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events). Once removed, the events are no longer available to be read, and can't be recovered. Though the Event Hubs service is free to remove events older than the retention period, it doesn't do so deterministically. There's no guarantee of when events will be removed.
 
 ```csharp
 try
@@ -122,7 +122,7 @@ finally
 
 This example makes use of the `ReadEvents` method of the `EventHubConsumerClient`, which allows it to see events from all [partitions](event-hubs-features.md#partitions) of an event hub. While it's convenient to use for exploration, we strongly recommend not using it for production scenarios. The `ReadEvents` method doesn't guarantee fairness amongst the partitions during iteration. Partitions compete with each other to publish events to be read. Depending on how service communication takes place, there may be a clustering of events per partition and a noticeable bias for a given partition or subset of partitions.
 
-To read from all partitions in a production application, we recommend preferring the [EventProcessorClient](/dotnet/api/azure.messaging.eventhubs.eventprocessorclient) or a custom [EventProcessor<TPartition>](/dotnet/api/azure.messaging.eventhubs.primitives.eventprocessor-1) implementation.
+To read from all partitions in a production application, we recommend preferring the [EventProcessorClient](/dotnet/api/azure.messaging.eventhubs.eventprocessorclient) or a custom [EventProcessor&ltTPartition&gt](/dotnet/api/azure.messaging.eventhubs.primitives.eventprocessor-1) implementation.
 
 ## Next steps
 See the following quickstarts and samples.