From 41fce372006696117864401d4c1c0c02702f0152 Mon Sep 17 00:00:00 2001
From: Francois Gouget
Date: Sun, 31 Dec 2006 19:39:41 +0000
Subject: [PATCH] Assorted spelling fixes
---
README | 8 ++---
admin/adminTestResults.php | 52 ++++++++++++++++-----------------
appsubmit.php | 8 ++---
cron/cleanup.php | 4 +--
help/maintainer_guidelines.help | 34 ++++++++++-----------
help/maintainer_ratings.help | 4 +--
include/application.php | 8 ++---
include/bugs.php | 2 +-
include/distribution.php | 14 ++++-----
include/image.php | 24 +++++++--------
include/monitor.php | 8 ++---
include/screenshot.php | 4 +--
include/testData.php | 52 ++++++++++++++++-----------------
include/url.php | 2 +-
include/version.php | 14 ++++-----
testResults.php | 30 +++++++++----------
unit_test/test_user.php | 4 +--
17 files changed, 136 insertions(+), 136 deletions(-)
diff --git a/README b/README
index d5e7917..19c8046 100644
--- a/README
+++ b/README
@@ -32,7 +32,7 @@ To install locally for testing/hacking:
short_open_tag 0
register_long_arrays 0
magic_quotes_gpc 0
- Or ensure your appdb directory has AllowOveride' set to 'All' inside
+ Or ensure your appdb directory has AllowOverride' set to 'All' inside
httpd.conf to let .htaccess set these settings.
# An AppDB admin user has been automatically created while running
@@ -42,12 +42,12 @@ To install locally for testing/hacking:
You should change the password as soon as possible!
#------------------------------------------------------------------------#
-You can create ether set up a real bugzilla database or a fake one
-
+You can either set up a real bugzilla database or a fake one
+#
# cd tables, run ./create_bugzilla_tables to create the fake bugzilla tables
#------------------------------------------------------------------------#
# or installing a real bugzilla database (hope this helps)
-
+#
# download buzilla (password for cvs is cvs)
cd /var/www/html
diff --git a/admin/adminTestResults.php b/admin/adminTestResults.php
index a184018..cc38b6f 100644
--- a/admin/adminTestResults.php
+++ b/admin/adminTestResults.php
@@ -31,18 +31,18 @@ if ($aClean['sSub'])
$oTest = new testData($aClean['iTestingId']);
$oTest->GetOutputEditorValues($_REQUEST);
- if($aClean['sSub'] == 'Submit') // submit the testing results
+ if($aClean['sSub'] == 'Submit') // submit the test results
{
$oTest->update(true);
$oTest->unQueue();
- } else if($aClean['sSub'] == 'Save') // save the testing results
+ } else if($aClean['sSub'] == 'Save') // save the test results
{
$oTest->update();
- } else if($aClean['sSub'] == 'Reject') // reject testing results
+ } else if($aClean['sSub'] == 'Reject') // reject test results
{
$oTest->update(true);
$oTest->Reject();
- } else if($aClean['sSub'] == 'Delete') // delete testing results
+ } else if($aClean['sSub'] == 'Delete') // delete test results
{
$oTest->delete();
}
@@ -64,18 +64,18 @@ if ($aClean['sSub'])
switch($oTest->sQueued)
{
case "true":
- apidb_header("Edit new testing results for ".$sVersionInfo);
+ apidb_header("Edit new test results for ".$sVersionInfo);
break;
case "rejected":
- apidb_header("Edit rejected testing results for ".$sVersionInfo);
+ apidb_header("Edit rejected test results for ".$sVersionInfo);
break;
case "false":
- apidb_header("Edit testing results for ".$sVersionInfo);
+ apidb_header("Edit test results for ".$sVersionInfo);
break;
}
echo '
";
echo "Please do not forget to mention which Wine version you used, how well it worked\n";
echo "and if any workarounds were needed. Having app descriptions just sponsoring the app\n";
echo "(yes, some vendors want to use the appdb for this) or saying ‘I haven’t tried this app with Wine’ ";
echo "will not help Wine development or Wine users.
\n";
echo "Please only submit applications/versions that you have tested.\n";
- echo "Submissions without testing information or not using the provided template will be rejected.\n";
+ echo "Submissions without test information or not using the provided template will be rejected.\n";
echo "If you are unable to see the in-browser editors below, please try Firefox, Mozilla or Opera browsers.\n";
echo "After your application has been added, you will be able to submit screenshots for it, post";
echo " messages in its forums or become a maintainer to help others trying to run the application.
";
@@ -139,7 +139,7 @@ if ($aClean['sSub'])
util_redirect_and_exit($_SERVER['PHP_SELF']);
}
- // Get the Testing results if they exist
+ // Get the Test results if they exist
$hResult = query_parameters("Select testingId from testResults where versionId = '?'",
$oVersion->iVersionId);
if($hResult)
diff --git a/cron/cleanup.php b/cron/cleanup.php
index 05e8a17..f002a5a 100644
--- a/cron/cleanup.php
+++ b/cron/cleanup.php
@@ -30,7 +30,7 @@ if($hUsersToWarn)
{
$oUser = new User($oRow->userid);
- /* if we get back true the user was warned and flaged as being warned */
+ /* if we get back true the user was warned and flagged as being warned */
/* if we get back false we didn't warn the user and didn't flag the user as warned */
/* because they have data associated with their account */
if($oUser->warnForInactivity())
@@ -56,7 +56,7 @@ if($hUsersToDelete)
deleteUser($oRow->userid);
} else
{
- /* is the user a maintainer? if so remove their maintainer privilages */
+ /* is the user a maintainer? if so remove their maintainer privileges */
if($oUser->isMaintainer())
{
Maintainer::deleteMaintainer($oUser);
diff --git a/help/maintainer_guidelines.help b/help/maintainer_guidelines.help
index 797733d..99915dc 100644
--- a/help/maintainer_guidelines.help
+++ b/help/maintainer_guidelines.help
@@ -3,11 +3,11 @@
Maintainers Guidelines
-This page gives informations on how to maintain an application once being an application maintainer. If you are looking on informations on how to become an application maintainer, this topic is covered in the FAQ.
+This page gives information on how to maintain an application once you are an application maintainer. If you are looking for information on how to become an application maintainer, this topic is covered in the FAQ.
-Getting a (super) maintainer gives you certain rights on the Application Database. However as you may know, with great power, comes great responsibility...
+Becoming a (super) maintainer gives you certain rights on the Application Database. However as you may know, with great power, comes great responsibility...
An application maintainer is someone who runs the application regularly and who is willing to be active in reporting regressions with newer versions of Wine and to help other users run this application under Wine.
@@ -22,14 +22,14 @@ You are expected to:
You will:
- Receive an email anytime a comment is posted or deleted for the application or the application information is modified
-- Be able to modify all aspects of your application(s) and version(s), including description, screenshots, how-to's, notes, comments, etc.
+- Be able to modify all aspects of your application(s) and version(s), including the description, screenshots, how-tos, notes, comments, etc.
Application overview page guidlines
N.B. Only super maintainers can change the general description of an application.
-You can edit an application overview page by clicking on the "Edit Application" button in an application overview page. You'll be then presented with a form whose fields are explained thereafter.
+You can edit an application overview page by clicking on the "Edit Application" button in the application overview page. You will be then presented with a form whose fields are explained thereafter.
-
Application name should be checked against official application name and should not contain the vendor's name.
@@ -38,10 +38,10 @@ Application name should be checked against official application name and should
Application vendor should be set correctly. If the vendor is missing, please contact appdb@winehq.org.
-
-Keywords are used by the search engine, you don't need to repeat the application's name but you are encouraged to provide some keywords in this field.
+Keywords are used by the search engine. You don't need to repeat the application's name but you are encouraged to provide some keywords in this field.
-
-Description should describe the application in a general manner (what it does). Wine and version specific considerations goes in version-specific pages (described below). If you want to add more than a short sentence, please add a cariage return after the first sentence as it will be used when showing application summary in the search engine, top-25 page and so on.
You are encouraged to make use of the template provided for application description; you can copy/paste this template from the "Submit application page".
+Description should describe the application in a general manner (what it does). THe Wine and version specific considerations go in version-specific pages (described below). If you want to add more than a short sentence, please add a cariage return after the first sentence as it will be used when showing the application summary in the search engine, top-25 page and so on.
You are encouraged to make use of the template provided for application description; you can copy/paste this template from the "Submit application page".
-
Webpage should contain the home page for this application. Please remember that an URL starts with http://.
@@ -51,17 +51,17 @@ Webpage should contain the home page for this application. Please remember that
Version page guidlines
-You can edit a version page by clicking on the "Edit Version" button in any version page for which you are a (super) maintainer. You'll be then presented with a form whose fields are explained thereafter.
+You can edit a version page by clicking on the "Edit Version" button in any version page for which you are a (super) maintainer. You will then be presented with a form whose fields are explained thereafter.
-
-Version name should be checked against official version name. However if you feel that two minor revision of an application will share the same problems or success, you are encouraged to use wildcards in the version number to don't fill the database with hundreds of versions. For example if you know that Adobe Acrobat 6.0, 6.01 and 6.1 are about the same application, just choose 6.x as a version name. You can however use the full version name in an history table in the description field (see below).
+Version name should be checked against official version name. However if you feel that two minor revisions of an application will share the same problems or success, you are encouraged to use wildcards in the version number to avoid cluttering the database with hundreds of versions. For example if you know that Adobe Acrobat 6.0, 6.01 and 6.1 are about the same application, just choose 6.x as a version name. You can however use the full version name in an history table in the description field (see below).
-
-Description should describe the application version and not be a repetition of the application description. Please use a short sentence as the first line of your description to describe what this version is and then add a cariage return after this first sentence as it will be used when showing version summary in the application page for example.
You are encouraged to make use of the template provided for version description; you can copy/paste this template from the "Submit version page".
-As you'll see in this template usefull informations to place in this field are the specification of what works and what doesn't in wine and you can also add what is called an history table to keep track of improvemetns and regression. Using the html editor described later in this document and the provided template it is easy to produce such a table which will contains columns like version number, wine version, installs, runs, rating. You can then use the styles drop down list of the editor to set the color of the row according to the rating (gold, silver, bronze or garbage). You can see an example here.
+Description should describe the application version and not be a repetition of the application description. Please use a short sentence as the first line of your description to describe what this version is, and then add a carriage return after this first sentence as it will be used when showing version summary, in the application page for example.
You are encouraged to make use of the template provided for version description; you can copy/paste this template from the "Submit version page".
+As you'll see in this template, useful information to place in this field is the specification of what works and what doesn't in wine. You can also add what is called an history table to keep track of improvements and regression. Using the html editor, described later in this document, and the provided template, it is easy to produce such a table which will contains columns with the version number, wine version, installs, runs, ratings. You can then use the styles drop down list of the editor to set the color of the row according to the rating (gold, silver, bronze or garbage). You can see an example here.
-
-Rating let's you rate how this version ran with the latest Wine version you tested it with. For rating definitions, please see this page.
+Rating lets you rate how this version ran with the latest Wine version you tested. For rating definitions, please see this page.
-
Release is the latest release of Wine you tested this version with.
@@ -70,33 +70,33 @@ Release is the latest release of Wine you tested this version with.
Additional URLs guidlines
-In both application and version editing page you can add additional URLs. These URLs can for example help the user find native alternatives for this application (in application overview page) or find specific dll (in version page).
+In both application and version editing pages you can add additional URLs. These URLs can, for example, help the user find native alternatives for this application (in application overview page) or find specific dlls (in version page).
Screenshots guidlines
-As a maintainer you are encouraged to provide screenshots for the versions you tested under Wine. To add a screenshot, simply click on the screenshot thumbnail you'll find in the version page you want to provide a screenshot for.
+As a maintainer you are encouraged to provide screenshots for the versions you tested under Wine. To add a screenshot, simply click on the screenshot thumbnail in the version page.
Notes guidlines
-In the version page you can add, edit and delete notes for the versions you maintain. Just click on "Add note" button.
+In the version page you can add, edit and delete notes for the versions you maintain. Just click on the "Add note" button.
How-to guidlines
-How-to's are just a special kind of notes. You can provide step-by-step explanations on how to install or run a specific version of the current application here. Please try to keep How-to's up to date (for example some steps might not be needed anymore using a more recent version of Wine).
+How-tos are just a special kind of notes. You can provide step-by-step explanations on how to install or run a specific version of the current application here. Please try to keep How-to's up to date (for example some steps might not be needed anymore using a more recent version of Wine).
Warnings guidlines
-Warnings are just a special kind of note. Warnings appear in red and should catch the attention of the reader. If you are warning users agains potential data corruption for example, please keep the warning up-to-date if it is not true anymore using a recent Wine version (in this case you might choose to keep the warning and tell users that since Wine X.Y, this has been fixed).
+Warnings are just a special kind of note. Warnings appear in red to catch the attention of the reader. They can be used to warning users against potential data corruption for instance. Please keep the warning up-to-date, especially if it is not true anymore using a recent Wine version (in this case you might choose to keep the warning and tell users that since Wine X.Y, this has been fixed).
Comments guidlines
-As a maintainer you are entitled to delete comments. Use this feature wisely and always explain why you deleted a comment. If a comment is useless or is not true anymore, you can safely delete it. Whenever you can, extract how-to's, other people's tests (for you test history table for example) from the comments and put it in your version's page and how-to notes.
+As a maintainer you are entitled to delete comments. Use this feature wisely and always explain why you deleted a comment. If a comment is useless or is not true anymore, you can safely delete it. Whenever you can, extract how-tos, other peoples tests (for your test history table for example) from the comments and put it in your versions page and how-to notes.
diff --git a/help/maintainer_ratings.help b/help/maintainer_ratings.help
index f6abb1d..c95740c 100644
--- a/help/maintainer_ratings.help
+++ b/help/maintainer_ratings.help
@@ -38,9 +38,9 @@ Application works, but it has some issues, even for normal use; a game may not r
- Garbage
-An app gets this rating if it can not be used for the purpose it was designed.
+An app gets this rating if it cannot be used for the purpose it was designed for.
There should be at least one bug report in bugzilla if an app gets this rating.
-Application doesn't start, or starts but has so many errors that it is nearly impossible to use it
+Application doesn't start, or starts but has so many errors that it is nearly impossible to use it.
diff --git a/include/application.php b/include/application.php
index 622b3cd..043eb5d 100644
--- a/include/application.php
+++ b/include/application.php
@@ -303,7 +303,7 @@ class Application {
"false", str_replace(" *** ","",$this->sKeywords), $this->iAppId))
{
$this->sQueued = 'false';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter();
$this->SendNotificationMail();
@@ -331,11 +331,11 @@ class Application {
"rejected", $this->iAppId))
{
$this->sQueued = 'rejected';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter("reject");
$this->SendNotificationMail("reject");
- // the application has been rejectedd
+ // the application has been rejected
addmsg("The application has been rejected.", "green");
}
}
@@ -348,7 +348,7 @@ class Application {
"true", $this->iAppId))
{
$this->sQueued = 'true';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->SendNotificationMail();
// the application has been re-queued
diff --git a/include/bugs.php b/include/bugs.php
index 514e93a..8c6c3c1 100644
--- a/include/bugs.php
+++ b/include/bugs.php
@@ -180,7 +180,7 @@ class Bug {
"false", $this->iLinkId))
{
$this->bQueued = false;
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter();
$this->SendNotificationMail();
// the Bug has been unqueued
diff --git a/include/distribution.php b/include/distribution.php
index caaf2aa..638d8cb 100644
--- a/include/distribution.php
+++ b/include/distribution.php
@@ -5,7 +5,7 @@
require_once(BASE."include/mail.php");
require_once(BASE."include/util.php");
-// Testing class for handling Distributions.
+// Test class for handling Distributions.
class distribution{
var $iDistributionId;
@@ -182,7 +182,7 @@ class distribution{
"false", $this->iDistributionId))
{
$this->sQueued = 'false';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter("unQueue");
$this->SendNotificationMail();
return true;
@@ -209,7 +209,7 @@ class distribution{
"rejected", $this->iDistributionId))
{
$this->sQueued = 'rejected';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
if(!$bSilent)
{
$this->mailSubmitter("reject");
@@ -240,10 +240,10 @@ class distribution{
"true", $this->iDistributionId))
{
$this->sQueued = 'true';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->SendNotificationMail();
- // the testing data has been resubmitted
+ // the test data has been resubmitted
addmsg("The Distribution has been resubmitted", "green");
return true;
}
@@ -320,10 +320,10 @@ class distribution{
$sMsg .= $aClean['sReplyText']."\n"; // append the reply text, if there is any
}
addmsg("The Distribution was successfully added into the database.", "green");
- } else // testing data queued.
+ } else // test data queued.
{
$sSubject = "Distribution ".$this->sName." submitted by ".$_SESSION['current']->sRealname;
- $sMsg .= "This testing data has been queued.";
+ $sMsg .= "This test data has been queued.";
$sMsg .= "\n";
addmsg("The Distribution you submitted will be added to the database after being reviewed.", "green");
}
diff --git a/include/image.php b/include/image.php
index 883ec2e..3ca29fb 100644
--- a/include/image.php
+++ b/include/image.php
@@ -66,7 +66,7 @@ class Image {
* isLoaded()
* This function should always be checked after loading a file
* with the constructor. Returns true if the image has been
- * succesfully loaded.
+ * successfully loaded.
*/
function isLoaded()
{
@@ -235,8 +235,8 @@ class Image {
$g = hexdec(substr($sBorderColor, 3, 2));
$b = hexdec(substr($sBorderColor, 5, 2));
- /* We multiply the border width by two because there are are borders
- at both sides */
+ /* We multiply the border width by two because there are borders
+ on both sides */
// GD 2.x
if(function_exists("imagecreatetruecolor"))
{
@@ -276,7 +276,7 @@ class Image {
/**
* add_watermark()
*
- * $watermark is a image resource identifier to any image resource.
+ * $watermark is an image resource identifier to any image resource.
*
* $min_mark_wwidth and $min_mark_height are the minimum sizes of the
* destination image before the watermark is added. If none are set
@@ -306,10 +306,10 @@ class Image {
}
/**
- * Output the image to a file set with $store.
+ * Save the image to a file set with $store.
*
* $iType is optional and is set like the second index of getimagesize().
- * If none (or 0) is set the orginal type of the file is used.
+ * If none (or 0) is set the original type of the file is used.
* If $store is not give, the current file name will be used.
* $quality is the jpeg output quality (100 best, 0 worst). Default is 75
*/
@@ -324,16 +324,16 @@ class Image {
{
case 2:
imagejpeg($this->oImage, $sOutputFilename, $iQuality);
- $this->set_debuglog("Outputed file as jpeg to $sOutputFilename");
+ $this->set_debuglog("Saved file as jpeg to $sOutputFilename");
break;
case 3:
imagepng($this->oImage, $sOutputFilename);
- $this->set_debuglog("Outputed file as png to $sOutputFilename");
+ $this->set_debuglog("Saved file as png to $sOutputFilename");
break;
default:
- $this->set_debuglog("Unkown output type");
+ $this->set_debuglog("Unknown output type");
return;
}
@@ -346,7 +346,7 @@ class Image {
* If $bHeader is true a Content-type header with the correct type
* is set.
* $iType is optional and is set like the second index of getimagesize().
- * If none (or 0) is set the orginal type of the file is used.
+ * If none (or 0) is set the original type of the file is used.
*
* $iQuality is the jpeg output quality (100 best, 0 worst)
*/
@@ -372,7 +372,7 @@ class Image {
break;
default:
- $this->set_debuglog("Unkown output type");
+ $this->set_debuglog("Unknown output type");
}
}
@@ -429,7 +429,7 @@ class ImageResource extends Image {
$this->iHeight = imagesy($oImage);
$this->iType = $iType;
- $this->set_debuglog("New image class created with as $oImage as"
+ $this->set_debuglog("New image class created with $oImage as"
." image resource and $iType as type. Dimensions"
." {$this->iWidth}x{$this->iHeight}");
}
diff --git a/include/monitor.php b/include/monitor.php
index 10c8f0f..ead1ead 100644
--- a/include/monitor.php
+++ b/include/monitor.php
@@ -109,12 +109,12 @@ class Monitor {
$sSubject = "Monitor for ".$sAppName;
$sSubject .= " added: ".$_SESSION['current']->sRealname;
$sMsg .= APPDB_ROOT."appview.php?iVersionId=".$this->iVersionId."\n";
- addmsg("You will now recieve an email whenever changes are made to this Application version.", "green");
+ addmsg("You will now receive an email whenever changes are made to this Application version.", "green");
} else
{
$sSubject = "Monitor for ".$sAppName." added: ".$_SESSION['current']->sRealname;
$sMsg .= APPDB_ROOT."appview.php?iAppId=".$this->iAppid."\n";
- addmsg("You will now recieve an email whenever changes are made to this Application.", "green");
+ addmsg("You will now receive an email whenever changes are made to this Application.", "green");
}
break;
case "delete":
@@ -123,12 +123,12 @@ class Monitor {
$sSubject = "Monitor for ".$sAppName;
$sSubject .= " removed: ".$_SESSION['current']->sRealname;
$sMsg .= APPDB_ROOT."appview.php?iVersionId=".$this->iVersionId."\n";
- addmsg("You will no longer recieve an email whenever changes are made to this Application version.", "green");
+ addmsg("You will no longer receive an email whenever changes are made to this Application version.", "green");
} else
{
$sSubject = "Monitor for ".$sAppName." removed: ".$_SESSION['current']->sRealname;
$sMsg .= APPDB_ROOT."appview.php?iAppId=".$this->iAppid."\n";
- addmsg("You will no longer recieve an email whenever changes are made to this Application.", "green");
+ addmsg("You will no longer receive an email whenever changes are made to this Application.", "green");
}
break;
}
diff --git a/include/screenshot.php b/include/screenshot.php
index 1e3f9f8..e6782a9 100644
--- a/include/screenshot.php
+++ b/include/screenshot.php
@@ -164,7 +164,7 @@ class Screenshot {
"false", $this->iScreenshotId))
{
$this->bQueued = false;
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter();
$this->mailMaintainers();
// the screenshot has been unqueued
@@ -198,7 +198,7 @@ class Screenshot {
/**
* This method generates a watermarked screenshot and thumbnail from the original file.
- * Usefull when changing thumbnail, upgrading GD, adding an image, etc.
+ * Useful when changing thumbnail, upgrading GD, adding an image, etc.
* Return false if an image could not be loaded.
*/
function generate()
diff --git a/include/testData.php b/include/testData.php
index 7e7380e..628500c 100644
--- a/include/testData.php
+++ b/include/testData.php
@@ -1,10 +1,10 @@
iVersionId);
if(!$_SESSION['current']->hasPriv("admin") &&
!$_SESSION['current']->hasAppVersionModifyPermission($oVersion))
@@ -100,7 +100,7 @@ class testData{
// Update Test Results.
function update($bSilent=false)
{
- // is the current user allowed to update this testing result?
+ // is the current user allowed to update this test result?
$oVersion = new Version($this->iVersionId);
if(!$_SESSION['current']->hasPriv("admin") &&
!$_SESSION['current']->hasAppVersionModifyPermission($oVersion) &&
@@ -146,10 +146,10 @@ class testData{
}
}
- // Delete testing results.
+ // Delete test results.
function delete($bSilent=false)
{
- // is the current user allowed to delete this testing result?
+ // is the current user allowed to delete this test result?
$oVersion = new Version($this->iVersionId);
if(!$_SESSION['current']->hasPriv("admin") &&
!$_SESSION['current']->hasAppVersionModifyPermission($oVersion) &&
@@ -157,13 +157,13 @@ class testData{
{
return;
}
- // now delete the testing data
+ // now delete the test data
$sQuery = "DELETE FROM testResults
WHERE testingId = '?'
LIMIT 1";
if(!($hResult = query_parameters($sQuery, $this->iTestingId)))
{
- addmsg("Error removing the deleted testing data!", "red");
+ addmsg("Error removing the deleted test data!", "red");
}
if(!$bSilent)
@@ -174,10 +174,10 @@ class testData{
}
- // Move Testing Data out of the queue.
+ // Move Test Data out of the queue.
function unQueue()
{
- // is the current user allowed to delete this testing data?
+ // is the current user allowed to delete this test data?
$oVersion = new Version($this->iVersionId);
if(!$_SESSION['current']->hasPriv("admin") &&
!$_SESSION['current']->hasAppVersionModifyPermission($oVersion))
@@ -185,7 +185,7 @@ class testData{
return;
}
- // If we are not in the queue, we can't move the testing data out of the queue.
+ // If we are not in the queue, we can't move the test data out of the queue.
if(!$this->sQueued == 'true')
return false;
@@ -193,7 +193,7 @@ class testData{
"false", $this->iTestingId))
{
$this->sQueued = 'false';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter("unQueue");
$this->SendNotificationMail();
}
@@ -201,7 +201,7 @@ class testData{
function Reject()
{
- // is the current user allowed to delete this testing data?
+ // is the current user allowed to delete this test data?
$oVersion = new Version($this->iVersionId);
if(!$_SESSION['current']->hasPriv("admin") &&
!$_SESSION['current']->hasAppVersionModifyPermission($oVersion))
@@ -217,7 +217,7 @@ class testData{
"rejected", $this->iTestingId))
{
$this->sQueued = 'rejected';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->mailSubmitter("reject");
$this->SendNotificationMail("reject");
}
@@ -238,7 +238,7 @@ class testData{
"true", $this->iTestingId))
{
$this->sQueued = 'true';
- // we send an e-mail to intersted people
+ // we send an e-mail to interested people
$this->SendNotificationMail();
}
}
@@ -308,7 +308,7 @@ class testData{
if($this->iSubmitterId)
{
$oSubmitter = new User($this->iSubmitterId);
- $sMsg .= "This Testing data has been submitted by ".$oSubmitter->sRealname.".";
+ $sMsg .= "This Test data has been submitted by ".$oSubmitter->sRealname.".";
$sMsg .= "\n";
}
if($aClean['sReplyText'])
@@ -316,20 +316,20 @@ class testData{
$sMsg .= "Appdb admin reply text:\n";
$sMsg .= $aClean['sReplyText']."\n"; // append the reply text, if there is any
}
- addmsg("The testing data was successfully added into the database.", "green");
- } else // testing data queued.
+ addmsg("The test data was successfully added into the database.", "green");
+ } else // test data queued.
{
$sSubject = "Test Results submitted for version ".$oVersion->sName." of ".$oApp->sName." submitted by ".$_SESSION['current']->sRealname;
$sMsg .= $sBacklink;
- $sMsg .= "This testing data has been queued.";
+ $sMsg .= "This test data has been queued.";
$sMsg .= "\n";
- addmsg("The testing data you submitted will be added to the database after being reviewed.", "green");
+ addmsg("The test data you submitted will be added to the database after being reviewed.", "green");
}
break;
case "edit":
$sSubject = "Test Results modified for version ".$oVersion->sName." of ".$oApp->sName." submitted by ".$_SESSION['current']->sRealname;
$sMsg .= $sBacklink;
- addmsg("testing data modified.", "green");
+ addmsg("test data modified.", "green");
break;
case "delete":
$sSubject = "Test Results deleted for version ".$oVersion->sName." of ".$oApp->sName." submitted by ".$_SESSION['current']->sRealname;
@@ -340,7 +340,7 @@ class testData{
$sMsg .= $aClean['sReplyText']."\n"; // append the reply text, if there is any
}
- addmsg("testing data deleted.", "green");
+ addmsg("test data deleted.", "green");
break;
case "reject":
$sSubject = "Test Results rejected for version ".$oVersion->sName." of ".$oApp->sName." submitted by ".$_SESSION['current']->sRealname;
@@ -351,7 +351,7 @@ class testData{
$sMsg .= "Reason given:\n";
$sMsg .= $aClean['sReplyText']."\n"; // append the reply text, if there is any
}
- addmsg("testing data rejected.", "green");
+ addmsg("test data rejected.", "green");
break;
}
$sEmail = User::get_notify_email_address_list(null, $this->iVersionId);
@@ -399,7 +399,7 @@ class testData{
if($rowsUsed == 0)
return;
- echo 'Testing Results
',"\n";
+ echo '
Test Results
',"\n";
echo '