From bec894a53d387321cdfab9cf0479c2c488789ea8 Mon Sep 17 00:00:00 2001
From: Joe Gordon
Date: Wed, 27 Aug 2014 16:19:05 -0700
Subject: [PATCH] Cleanup tempest-logs.html
Correct a few typos and update the link to this file.
Change-Id: Ia8f22d458f7f985861050a52235230dc84c257e2
---
.../files/logs/help/tempest-logs.html | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/modules/openstack_project/files/logs/help/tempest-logs.html b/modules/openstack_project/files/logs/help/tempest-logs.html
index 7316870c9e..65df6efcc0 100644
--- a/modules/openstack_project/files/logs/help/tempest-logs.html
+++ b/modules/openstack_project/files/logs/help/tempest-logs.html
@@ -4,7 +4,7 @@
the current tempest run. Within them
should be everything you need to get to the bottom of a test
failure. The screen-* logs will be your most valuable tools in this
- process. Use the timestamp of a the failed test in
+ process. Use the timestamp of the failed test in
the current tempest run.
Nova Compute Fails
@@ -15,7 +15,7 @@
- screen-n-api.txt.gz - the nova
api log, which will show top level failures. Make sure the request
- that was being sent in actually suceeded.
+ that was being sent in actually succeeded.
- screen-n-cpu.txt.gz - the nova
compute log. If a libvirt or qemu issue happened during guest
creation it will be here.
@@ -32,7 +32,7 @@