Removed all tags (#4859)

Co-authored-by: David Boike <david.boike@gmail.com>

README.md

@@ -44,7 +44,6 @@ As part of a full review the following should be done:
  * All links are relevant. No 3rd party links have redirects or 404s.
  * Are there any more links that can be added to improve the content
  * Content is correct up to and including the current released version
- * Tags are correct
  * Summary and title is adequate
  * Update reviewed date in header, even if no changes were made.
 
@@ -74,9 +73,6 @@ For example:
 title: Auditing Messages
 summary: Provides built-in message auditing for every endpoint.
 versions: '[4,)'
-tags:
-- Auditing
-- Forwarding Messages
 related:
 - samples/custom-checks/monitoring3rdparty
 redirects:
@@ -139,28 +135,6 @@ summary: Provides built-in message auditing for every endpoint.
 Optional. Used for the meta description tag (`<meta name="description" />`) and displaying the search results.
 
 
-### Tags
-
-```
-tags:
-- Auditing
-- Forwarding Messages
-```
-
-Optional. Used to flag the article as being part of a group of articles.
-
-Tags are rendered in the articles content with the full list of tags being rendered at [https://docs.particular.net/tags](https://docs.particular.net/tags). Untagged articles will be rendered here [https://docs.particular.net/tags/untagged](https://docs.particular.net/tags/untagged)
-
-Tags are interpreted in two ways.
-
-* For inclusion in URLs:
-   * Tag are lower case
-   * Spaces are replaced with dashes (`-`)
-* For display purposes:
-   * Tags are lower case
-   * Dashes (`-`) are replaced with spaces
-
-
 ### Hidden
 
 ```
@@ -249,9 +223,6 @@ To mark a page as belonging to the [Particular Software Learning Path](https://p
 ---
 title: ServiceInsight Interaction
 summary: 'Using ServiceInsight Together'
-tags:
-- Invocation
-- Debugging
 redirects:
 - servicecontrol/sc-si
 - servicecontrol/debugging-servicecontrol

nservicebus/architecture/scaling.md

@@ -1,9 +1,6 @@
 ---
 title: Scaling with NServiceBus
 summary: NServiceBus provides several options to scale out a system
-tags:
- - scalability
- - routing
 redirects:
  - transports/scale-out
 reviewed: 2019-06-13
@@ -66,4 +63,4 @@ Execute the following steps to upgrade an endpoint without downtime:
 2. Take down one endpoint instance of `Finance` and upgrade it to version 2 of the message assembly `Finance.Messages`. During this time, `Sales` can continue sending messages and the running endpoint instance for `Finance` can continue processing them.
 3. Bring the upgraded version of `Finance` back up so it can start processing version 1 messages.
 4. Take down the still-running version 1 of `Finance` and upgrade it as well to version 2 of `Finance.Messages`
-5. Update `Sales` to also have message assembly `Finance.Messages` version 2.
+5. Update `Sales` to also have message assembly `Finance.Messages` version 2.

nservicebus/azure/index.md

@@ -1,8 +1,6 @@
 ---
 title: NServiceBus and Azure
 summary: Using Azure for endpoint hosting and to provide Transports and Persistence
-tags:
-- Azure
 reviewed: 2019-01-15
 ---
 
@@ -37,4 +35,4 @@ NServiceBus helps create distributed .NET systems not only on premises but also
 ## Cloud native extensions and samples
 
  * [Azure Blob Storage Data Bus](/samples/azure/blob-storage-databus/)
- * [Azure Service Fabric Partition Aware Routing](/samples/azure/azure-service-fabric-routing/)
+ * [Azure Service Fabric Partition Aware Routing](/samples/azure/azure-service-fabric-routing/)

nservicebus/azure/understanding-transactionality-in-azure.md

@@ -1,11 +1,6 @@
 ---
 title: Understanding Transactions in Azure
 summary: Things to keep in mind when using transactions with NServiceBus in Azure
-tags:
-- Azure
-- Transactions
-- Idempotency
-- DTC
 redirects:
  - nservicebus/transactions
  - nservicebus/understanding-transactions-in-windows-azure
@@ -50,4 +45,4 @@ Note that this protocol requires two communication steps for each resource manag
  * Using two communication steps per resource manager results in additional communication: 2 resources - 4 network calls, 4 resources - 16 calls, 100 resources - 400 calls, etc. This limits scalability.
  * Azure data centers consist of hundreds of thousands of machines; failure needs to be expected and all systems must be able to deal with network partitions. Network partitions result in slow or [in doubt](https://msdn.microsoft.com/en-us/library/ms681727.aspx) transactions. Therefore the requirement to wait for responses from all resource managers is problematic even if the communication overhead is manageable.
 
-The latter is the primary reason why none of the Azure services supports distributed transactions, and the recommendation is not to use them in new designs even if it's technically possible.
+The latter is the primary reason why none of the Azure services supports distributed transactions, and the recommendation is not to use them in new designs even if it's technically possible.

nservicebus/azure/ways-to-live-without-transactions.md

@@ -3,11 +3,6 @@ title: Avoiding Transactions in Azure
 summary: Options for avoiding transactions in Azure
 reviewed: 2020-02-20
 isLearningPath: true
-tags:
- - Azure
- - Transactions
- - Idempotency
- - DTC
 ---
 
 Some [transports](/transports/) in NServiceBus rely on the [Distributed Transaction Coordinator (DTC)](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ms684146(v=vs.85)) to make a distributed system reliable and to ensure consistency. In Azure, DTC should be avoided since many services don't support transactions, as explained in [Understanding Transactionality in Azure](understanding-transactionality-in-azure.md).
@@ -158,4 +153,4 @@ Arguably this is a risky approach that can lead to subtle errors. Although it's
 
 In some systems it is possible to accept uncertainty and potential inaccuracies caused by non-idempotent messages. In some cases the data doesn't have to be consistent at all times. In other systems there might be mechanisms that allow for dealing with inconsistencies afterwards.
 
-Although that might seem unacceptable for many programmers, in the end it is a business decision. It's always recommended to talk to business experts and double-check their expectations.
+Although that might seem unacceptable for many programmers, in the end it is a business decision. It's always recommended to talk to business experts and double-check their expectations.

nservicebus/compliance/gdpr.md

@@ -4,8 +4,6 @@ summary: Information about PII stored by NServiceBus
 versions: "[5,)"
 component: core
 isLearningPath: true
-tags:
- - Compliance
 reviewed: 2020-03-30
 ---
 
@@ -76,4 +74,4 @@ When this data needs to be deleted, contact [Particular Support](https://particu
 
 Data points such as "Endpoint Name" have been mentioned multiple times in this document. It's important to note that in many situations these pieces of data do not need to be considered with regards to GDPR. However, if that data has been configured to include PII, they will. It is best to avoid naming things in a manner that includes PII.
 
-There are situations where this is not possible. For example, when using MSMQ as a transport the [computer's name will be included in the name of the queues](/transports/msmq/full-qualified-domain-name.md). This is a requirement of MSMQ and, as a result, means that queue names should receive the same vetting as machine names.
+There are situations where this is not possible. For example, when using MSMQ as a transport the [computer's name will be included in the name of the queues](/transports/msmq/full-qualified-domain-name.md). This is a requirement of MSMQ and, as a result, means that queue names should receive the same vetting as machine names.

nservicebus/compliance/index.md

@@ -2,10 +2,8 @@
 title: Compliance
 summary: Compliance Table of Contents
 reviewed: 2020-03-16
-tags:
- - Compliance
 ---
 
 Systems built using NServiceBus often run in environments requiring high levels of government and/or regulatory compliance.
 
-* [General Data Protection Regulation (GDPR)](/nservicebus/compliance/gdpr.md)
+* [General Data Protection Regulation (GDPR)](/nservicebus/compliance/gdpr.md)

nservicebus/dependency-injection/autofac.md

@@ -3,8 +3,6 @@ title: Autofac
 summary: Details on how to Configure NServiceBus to use Autofac for dependency injection. 
 component: Autofac
 reviewed: 2020-02-20
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/autofac
 redirects:

nservicebus/dependency-injection/castlewindsor.md

@@ -3,8 +3,6 @@ title: Castle Windsor
 summary: Details on how to Configure NServiceBus to use Castle Windsor for dependency injection.
 component: Castle
 reviewed: 2020-02-20
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/castle
 redirects:

nservicebus/dependency-injection/extensions-dependencyinjection.md

@@ -3,8 +3,6 @@ title: NServiceBus.Extensions.DependencyInjection
 summary: Provides integration with the Microsoft.Extensions.DependencyInjection abstraction
 reviewed: 2020-02-17
 component: Extensions.DependencyInjection
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/extensions-dependency-injection
  - samples/hosting/generic-host
@@ -69,4 +67,4 @@ The `NServiceBus.Extensions.DependencyInjection` package does not support proper
 
 The package allows the container to be used in [externally managed mode](/nservicebus/dependency-injection/#externally-managed-mode) for full control of the dependency injection container via the `EndpointWithExternallyManagedServiceProvider` extension point:
 
-snippet: externally-managed-mode
+snippet: externally-managed-mode

nservicebus/dependency-injection/index.md

@@ -4,8 +4,6 @@ summary: NServiceBus automatically registers components, handlers, and sagas.
 component: Core
 isLearningPath: true
 reviewed: 2019-09-11
-tags:
- - Dependency Injection
 redirects:
  - nservicebus/containers
  - nservicebus/dependency-injection/msdependencyinjection
@@ -14,4 +12,4 @@ related:
 ---
 NServiceBus automatically registers and invokes message handlers, sagas, and other user-provided extension points using a dependency injection container.
 
-partial: ownership
+partial: ownership

nservicebus/dependency-injection/ninject.md

@@ -3,8 +3,6 @@ title: Ninject
 summary: Configure NServiceBus to use Ninject for dependency injection.
 reviewed: 2018-12-05
 component: Ninject
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/ninject
  - nservicebus/dependency-injection/child-lifetime

nservicebus/dependency-injection/simpleinjector.md

@@ -3,8 +3,6 @@ title: Simple Injector
 summary: Configure NServiceBus to use Simple Injector for dependency injection.
 component: SimpleInjector
 reviewed: 2018-12-05
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/simpleinjector
 redirects:

nservicebus/dependency-injection/spring.md

@@ -3,8 +3,6 @@ title: Spring
 summary: Details on how to Configure NServiceBus to use Spring for dependency injection. Includes usage examples as well as lifecycle mappings.
 component: Spring
 reviewed: 2018-12-05
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/spring
 redirects:

nservicebus/dependency-injection/structuremap.md

@@ -3,8 +3,6 @@ title: StructureMap
 summary: Details on how to Configure NServiceBus to use StructureMap for dependency injection.
 component: StructureMap
 reviewed: 2020-02-20
-tags:
- - Dependency Injection
 redirects:
  - nservicebus/containers/structuremap
 related:

nservicebus/dependency-injection/unity.md

@@ -3,8 +3,6 @@ title: Unity
 summary: Details on how to Configure NServiceBus to use Unity for dependency injection.
 component: Unity
 reviewed: 2020-02-20
-tags:
- - Dependency Injection
 related:
  - samples/dependency-injection/unity
 redirects:
@@ -24,4 +22,4 @@ partial: usage
 | [SingleInstance](/nservicebus/dependency-injection/)                                  | [`ContainerControlledLifetimeManager`](https://msdn.microsoft.com/en-us/library/microsoft.practices.unity.containercontrolledlifetimemanager.aspx)                          |
 
 
-include: property-injection
+include: property-injection

nservicebus/endpoints/decommissioning-endpoints.md

@@ -2,9 +2,6 @@
 title: Decommissioning Endpoints
 summary: Describes the process of permanently shutting down endpoints
 reviewed: 2020-03-23
-tags:
- - Endpoint
- - Endpoint Instance
 related:
  - samples/endpoint-configuration
 
@@ -21,4 +18,4 @@ When decommissioning endpoints, several aspects should be considered:
  1. Routing should be adjusted to make sure that no new messages will be delivered to that endpoint.
  1. All messages should be processed from the endpoint's queue.
  1. [Timeouts should be rerouted to other endpoint instances](/persistence/ravendb/reroute-existing-timeouts.md).
- 1. If any errors are discovered in the ServicePulse/ServiceControl tools, [redirect functionality](/servicepulse/redirect.md) can be used to reroute messages to another endpoint instance.
+ 1. If any errors are discovered in the ServicePulse/ServiceControl tools, [redirect functionality](/servicepulse/redirect.md) can be used to reroute messages to another endpoint instance.

nservicebus/endpoints/index.md

@@ -3,9 +3,6 @@ title: Endpoints
 summary: Describe the concepts of Endpoint and Endpoint Instance.
 reviewed: 2019-07-18
 component: Core
-tags:
-- Endpoint
-- Endpoint Instance
 related:
  - samples/endpoint-configuration
 redirects:
@@ -14,4 +11,4 @@ redirects:
 
 An _endpoint_ is a logical entity that communicates with other endpoints via [_messaging_](/nservicebus/messaging). Each endpoint has an identifying name and contains a collection of [_message handlers_](/nservicebus/handlers/) and [_sagas_](/nservicebus/sagas/). An endpoint can be deployed to a number of machines and environments. Each deployment of an endpoint is an instance. Each endpoint instance has an input queue which contains messages for the endpoint instance to process.
 
-It is common for each endpoint to have a single endpoint instance. As endpoints need to [scale-out](/nservicebus/architecture/scaling.md), additional endpoint instances can be added. This collection of endpoint instances still represents a single logical endpoint.
+It is common for each endpoint to have a single endpoint instance. As endpoints need to [scale-out](/nservicebus/architecture/scaling.md), additional endpoint instances can be added. This collection of endpoint instances still represents a single logical endpoint.

nservicebus/endpoints/specify-endpoint-name.md

@@ -3,8 +3,6 @@ title: Specify Endpoint Name
 summary: Describes the ways in which to specify an endpoint name
 reviewed: 2019-12-25
 component: Core
-tags:
-- Convention
 redirects:
 - nservicebus/how-to-specify-your-input-queue-name
 - nservicebus/messaging/specify-input-queue-name

nservicebus/gateway/scale-out.md

@@ -1,8 +1,6 @@
 ---
 title: Scale out
 reviewed: 2019-07-18
-tags:
- - scalability
 related:
  - samples/gateway
 ---
@@ -30,4 +28,4 @@ Handle HA requirements by setting the LB to fail over to another endpoint instan
 
 ## Caveats
 
-[Callbacks](/nservicebus/messaging/callbacks.md) through the gateway are not supported on scaled-out endpoints.
+[Callbacks](/nservicebus/messaging/callbacks.md) through the gateway are not supported on scaled-out endpoints.

nservicebus/handlers/accessing-data.md

@@ -9,9 +9,6 @@ related:
  - persistence/sql/accessing-data
  - persistence/mongodb
  - persistence/ravendb
-tags:
- - Persistence
- - Saga
 ---
 
 In most cases [handlers](/nservicebus/handlers/) are meant to modify the internal state of an application based on the received message. In a messaging system it is critical to make sure the state change is persisted exactly once. The scenarios below discuss in detail how NServiceBus transaction and persistence settings affect the way business data is stored.
@@ -86,4 +83,3 @@ and think about the behavior of the message processing:
  - If re-sending messages is implemented, multiple copies of the same message may be sent to the downstream endpoints  
  - If message identity is used for de-duplication, message IDs must be generated in a deterministic manner
  - If outgoing messages depend on the application state, **the code above is incorrect when messages can get re-ordered** (e.g. by infrastructure failures, [recoverability](/nservicebus/recoverability) or competing consumers)
-

nservicebus/hosting/azure-functions/index.md

@@ -1,8 +1,6 @@
 ---
 title: Azure Functions
 summary: Hosting NServiceBus in Azure Functions
-tags:
- - Hosting
 related:
  - samples/azure/functions
 reviewed: 2020-05-12
@@ -30,4 +28,4 @@ When using Azure Functions with Azure Service Bus (ASB) or Azure Storage Queues
 - The NServiceBus `ILog` logging abstraction and the Azure Functions `ILogger` are not wired to work together.
 - When using the default recoverability or specifying custom number of immediate retries, the number of delivery attempts specified on the underlying queue (ASB) or Azure Functions host (ASB) must be more than then number of the immediate retries. The Azure Functions defaults are 10 (`MaxDeliveryCount`) for the ASB trigger and 5 (`DequeueCount`) for the ASQ trigger.
 - Delayed Retries are supported only with Azure Service Bus, and not with Azure Storage Queues.
-- Message handlers have to be included in the the Azure Functions assembly.
+- Message handlers have to be included in the the Azure Functions assembly.

nservicebus/hosting/cloud-services-host/configuration.md

@@ -1,8 +1,6 @@
 ---
 title: Configuration
 summary: Configuring the endpoint when hosting in Azure cloud services
-tags:
-- Azure
 reviewed: 2020-02-27
 ---
 
@@ -81,4 +79,4 @@ Azure cloud services allow changing the configuration settings from within the A
 
 If configuration changes should result in a reconfiguration of the endpoint, consider instructing the `RoleEnvironment` to restart the role instances by subscribing to the [RoleEnvironment.Changing event](https://msdn.microsoft.com/en-us/library/microsoft.windowsazure.serviceruntime.roleenvironment.changing.aspx) and setting `e.Cancel = true;`
 
-If at least two role instances are running, this will result in a configuration change without inflicting downtime on the overall system. Each instance may reboot individually in the process, but this is orchestrated across update and fault domains so that at any point in time an instance is operational.
+If at least two role instances are running, this will result in a configuration change without inflicting downtime on the overall system. Each instance may reboot individually in the process, but this is orchestrated across update and fault domains so that at any point in time an instance is operational.

nservicebus/hosting/cloud-services-host/critical.md

@@ -3,9 +3,6 @@ title: Critical Error Behavior
 summary: Handling Critical errors in Azure Cloud Services
 component: CloudServicesHost
 reviewed: 2019-11-04
-tags:
- - Hosting
- - Azure
 ---
 
 include: cloudserviceshost-deprecated-warning
@@ -23,4 +20,4 @@ The Azure host is terminated on critical errors by default. When the host is ter
 
 The Azure host is not terminated on critical errors by default and only shuts down the bus. This would cause the role not to process messages until the role host is restarted. To address this (probably undesired) behavior, implement a critical errors action that shuts down the host process instead.
 
-snippet: DefineCriticalErrorActionForAzureHost
+snippet: DefineCriticalErrorActionForAzureHost

nservicebus/hosting/cloud-services-host/faq.md

@@ -2,9 +2,6 @@
 title: Azure Cloud Services Host FAQ
 summary: Frequently asked questions related to the Azure Cloud Services host.
 component: CloudServicesHost
-tags:
-- Azure
-- Hosting
 reviewed: 2020-05-05
 ---
 
@@ -42,4 +39,4 @@ snippet: EndpointNameInCodeForAzureHost
 
 The cloud services role entry point takes care of updating these values, used for identification of the endpoint instance in ServiceControl, automatically, i.e. the `$.diagnostics.hostdisplayname` defaults to the role name and the `$.diagnostics.hostid` contains the instance ID.
 
-In web roles these values must be set manually, refer to [Override Host Id](/nservicebus/hosting/override-hostid.md) for more information on this topic.
+In web roles these values must be set manually, refer to [Override Host Id](/nservicebus/hosting/override-hostid.md) for more information on this topic.