[libtest-bdd-cucumber-perl] 09/25: fix Test::BDD::Cucumber::StepContext link in the tutorial pod

[Intrigeri]

This is an automated email from the git hooks/post-receive script.

intrigeri pushed a commit to branch master
in repository libtest-bdd-cucumber-perl.

commit 4d523d5d008a2087434a9a5299f985b14aeb6a65
Author: Chylli <chylli.email at gmail.com>
Date:   Fri Jan 30 13:13:32 2015 +0800

    fix Test::BDD::Cucumber::StepContext link in the tutorial pod
---
 lib/Test/BDD/Cucumber/Manual/Tutorial.pod | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/Test/BDD/Cucumber/Manual/Tutorial.pod b/lib/Test/BDD/Cucumber/Manual/Tutorial.pod
index 8f66be7..8de935c 100644
--- a/lib/Test/BDD/Cucumber/Manual/Tutorial.pod
+++ b/lib/Test/BDD/Cucumber/Manual/Tutorial.pod
@@ -152,7 +152,7 @@ it's called I<Check MD5>. Scenarios are marked out using the C<Scenario:>
 keyword, and just like the Background section before, it's a series of steps.
 
 These steps rely on the step before, which means we can examine the
-L<Test::Builder::StepContext|context> object C<$c> a little more closely.
+L<Test::BDD::Cucumber::StepContext|context> object C<$c> a little more closely.
 
  Given qr/a Digest (\S+) object/, sub {
     my $c = shift;
@@ -165,7 +165,7 @@ L<Test::Builder::StepContext|context> object C<$c> a little more closely.
 Creates a step definition. We create a new L<Digest> object, and then use
 L<Test::More>'s C<ok()> function to check that worked. We then put it in the
 I<stash> for other steps to use. There are three stashes documented in
-L<Test::Builder::StepContext>, C<feature>, C<scenario> and C<step>. As you might
+L<Test::BDD::Cucumber::StepContext>, C<feature>, C<scenario> and C<step>. As you might
 expect, C<feature> is available to all step definitions that are being executed
 as part of a feature, and C<scenario> is available to all steps that are being
 executed as part of a scenario.
@@ -173,7 +173,7 @@ executed as part of a scenario.
 The context is the single argument that gets passed to each step, and it
 contains evertything that step should need to execute. We'll be looking at some
 of the methods you can call against it as we look at other steps, and you can
-find complete documentation for it here: L<Test::Builder::StepContext>.
+find complete documentation for it here: L<Test::BDD::Cucumber::StepContext>.
 
 You'll note that the code above differs from the very first example, where we
 made use of C<C> and C<S>. C<C> is a function which returns the current context,

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libtest-bdd-cucumber-perl.git