diff --git a/data/registry/otel-odddotnet.yml b/data/registry/otel-odddotnet.yml
index aa62a9744246..1f223f07fc16 100644
--- a/data/registry/otel-odddotnet.yml
+++ b/data/registry/otel-odddotnet.yml
@@ -1,5 +1,5 @@
 # cSpell:ignore Kenna odddotnet
-title: OddDotNet OTel Collector Test Harness
+title: 'OddDotNet: Test Harness for OpenTelemetry'
 registryType: utilities
 language: collector
 tags:
@@ -17,8 +17,8 @@ urls:
 license: Apache 2.0
 description: OddDotNet is a Test Harness for OpenTelemetry that works for any
   language, built in .NET. It is a container image that accepts OpenTelemetry
-  signals over gRPC, and it includes a query language for
-  verifying and validating those signals.
+  signals over gRPC, and it includes a query language for verifying and
+  validating those signals.
 
   OddDotNet enables automated Observability Driven Development, hence where it
   gets its name.
diff --git a/data/registry/tools-odddotnet-client-dotnet.yml b/data/registry/tools-odddotnet-client-dotnet.yml
index b9908a3bfa8e..310137c19cc2 100644
--- a/data/registry/tools-odddotnet-client-dotnet.yml
+++ b/data/registry/tools-odddotnet-client-dotnet.yml
@@ -16,8 +16,8 @@ urls:
 license: Apache 2.0
 description: OddDotNet is an Test Harness for OpenTelemetry that works for any
   language, built in .NET. It is a container image that accepts OpenTelemetry
-  signals over gRPC, and it includes a query language for
-  verifying and validating those signals.
+  signals over gRPC, and it includes a query language for verifying and
+  validating those signals.
 
   While it's possible to generate your own client using the proto files, it is
   often more convenient to use a pre-compiled package installed from NuGet. This