From fd6213784ceadac7bf601889bc39ac45b027de36 Mon Sep 17 00:00:00 2001
From: Michael Boniface <mjb@it-innovation.soton.ac.uk>
Date: Mon, 4 Jun 2018 12:40:01 +0000
Subject: [PATCH] Update README.md

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 8aa004f..3a99361 100644
--- a/README.md
+++ b/README.md
@@ -62,14 +62,14 @@ SSH into the VM
 The containers are controlled using a script called /vagrant/scripts/test/fixtures.sh
 
 ```
-Usage: fixturs.sh create|start|stop|destroy [-f config_file] [-r repo_root] [-c service_name]"
+Usage: fixture.sh create|start|stop|destroy [-f config_file] [-r repo_root] [-c service_name]"
 ```
 
 To create all the services needed for integration tests
 
 ```
 sudo su
-/vagrant/scripts/test/fixtures.sh create -f /vagrant/src/test/clmctest/rspec.json
+/vagrant/scripts/test/fixture.sh create -f /vagrant/src/test/clmctest/rspec.json
 ```
 
 The containers created are defined an rspec.json file, there's an example here `/vagrant/src/test/clmctest/rspec.json`
@@ -79,7 +79,7 @@ The `fixtures.sh` script defaults to look for a rspec.json in the current direct
 To create|start|stop|destroy specific services use the -c option e.g.
 
 ```
-/vagrant/scripts/test/fixtures.sh create -f /vagrant/src/test/clmctest/rspec.json -c clmc-service
+/vagrant/scripts/test/fixture.sh create -f /vagrant/src/test/clmctest/rspec.json -c clmc-service
 ```
 
 Attach to the test-runner to run the tests
-- 
GitLab