README.md in test-tracer-1.2.0 vs README.md in test-tracer-1.2.1

@@ -32,11 +32,11 @@
 method. The method must return the wrapped item. You can customize the behaviour by implementing `Test::Wrapped::Extractor` and setting `wrapped_span_extractor` and/or `wrapped_span_context_extractor`.
 
 ### Usage
 
 ```ruby
-require "test/tracer"
+require "test-tracer"
 
 describe "Test::Tracer examples" do
   let(:tracer) { Test::Tracer.new }
 
   context "when we expect no traces" do
@@ -85,11 +85,11 @@
 The modification operations e.g. `operation_name=`, `set_tag`, `set_baggage_item` on a span are not allowed after it's finished. It throws `Test::Span::SpanAlreadyFinished` exception. The same with `finish`. The span can be finished only once.
 
 ### Usage
 
 ```ruby
-require "test/tracer"
+require "test-tracer"
 
 describe "Test::Span examples" do
   let(:tracer) { Test::Tracer.new }
 
   context "when a new span was started" do
@@ -154,10 +154,10 @@
 
 
 ### Usage
 
 ```ruby
-require "test/tracer"
+require "test-tracer"
 
 describe "Test::SpanContext examples" do
   let(:tracer) { Test::Tracer.new }
 
   context "when a new span was started as child of root" do