Recommend newer Message::Passing::Output::Search::Elasticsearch in docs

suretec · Feb 23, 2015 · 4731a19 · 4731a19
1 parent 4d5e5a4
commit 4731a19
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/Changes b/Changes
@@ -2,6 +2,7 @@
     Message::Passing::Manual::Components
   - Fix daemonize_if_needed spelling
   - Add documentation for all command line options
+  - Recommend newer Message::Passing::Output::Search::Elasticsearch in docs
 
 0.115 2014-08-23T09:55:00+03:00 YAPC::EU 2014 release
   - Fix internal and therefore undocumented type parameter swallows

diff --git a/README b/README
@@ -30,7 +30,7 @@ DESCRIPTION
     For a practical example, You generate events from a source (e.g. ZeroMQ
     output of logs and performance metrics from your Catalyst FCGI or
     Starman workers) and run one script that will give you a central
-    application log file, or push the logs into ElasticSearch.
+    application log file, or push the logs into Elasticsearch.
 
     There are a growing set of components you can plug together to make your
     solution.
@@ -95,8 +95,7 @@ COMPONENTS
     Message::Passing::Output::STOMP
     Message::Passing::Output::ZeroMQ
     Message::Passing::Output::WebHooks
-    Message::Passing::Output::ElasticSearch -
-    (<https://github.com/suretec/Message-Passing-Output-ElasticSearch>)
+    Message::Passing::Output::Search::Elasticsearch
     Message::Passing::Output::Redis
     Message::Passing::Output::Test
 

diff --git a/lib/Message/Passing.pm b/lib/Message/Passing.pm
@@ -127,7 +127,7 @@ manor.
 For a practical example, You generate events from a source (e.g.
 L<ZeroMQ> output of logs and performance metrics from your L<Catalyst> FCGI
 or L<Starman> workers) and run one script that will give you a central
-application log file, or push the logs into L<ElasticSearch>.
+application log file, or push the logs into Elasticsearch.
 
 There are a growing set of components you can plug together
 to make your solution.
@@ -215,7 +215,7 @@ Outputs send data to somewhere, i.e. they consume messages.
 
 =item L<Message::Passing::Output::WebHooks>
 
-=item L<Message::Passing::Output::ElasticSearch> - (L<https://github.com/suretec/Message-Passing-Output-ElasticSearch>)
+=item L<Message::Passing::Output::Search::Elasticsearch>
 
 =item L<Message::Passing::Output::Redis>