From a34bd10b1cbe56d526e00eab5103f01f8ca4449c Mon Sep 17 00:00:00 2001 From: Nick Silkey Date: Fri, 20 Dec 2013 13:13:03 -0600 Subject: [PATCH] small typo fix --- docs/source/docs/getting-started/next-steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/docs/getting-started/next-steps.md b/docs/source/docs/getting-started/next-steps.md index b9d0dd2d2..90d758517 100644 --- a/docs/source/docs/getting-started/next-steps.md +++ b/docs/source/docs/getting-started/next-steps.md @@ -17,6 +17,6 @@ From here, there are a few resources that can help you along your infrastructure * Write a blog post describing getting started with Test Kitchen, or an interesting problem Test Kitchen has allowed you to solve * Take a look at the excellent O'Reilly book [Test-driven Infrastructure with Chef](http://shop.oreilly.com/product/0636920030973.do) -One question that users often raise is: "How can I get Test Kitchen to test multiple machines?". Usually this question really means: I want to test the interaction between machines, for example a webserver and a database. It's important to understand that this is not the kind of testing that Test Kitchen was designed for. Acceptance testing of infrastructure stacks is valueable, fascinating and difficult - for an approach which makes use of Test Kitchen as a library, see [Leibniz](http://leibniz.cc). +One question that users often raise is: "How can I get Test Kitchen to test multiple machines?". Usually this question really means: I want to test the interaction between machines, for example a webserver and a database. It's important to understand that this is not the kind of testing that Test Kitchen was designed for. Acceptance testing of infrastructure stacks is valuable, fascinating and difficult - for an approach which makes use of Test Kitchen as a library, see [Leibniz](http://leibniz.cc). The rest of the documentation is a work in progress so bear with us. Better yet, if you've learned something and want to contribute, please **fork the docs**!