Skip to content

Commit

Permalink
Lots of minor speling corrections to documentation files.
Browse files Browse the repository at this point in the history
  • Loading branch information
@mgrdcm
mgrdcm committed Mar 11, 2011
1 parent 8e6efc6 commit 3081622
Show file tree
Hide file tree
Showing 7 changed files with 42 additions and 42 deletions.
28 changes: 14 additions & 14 deletions docbook/Admin_Guide/en-US/Configuration.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@
<varlistentry>
<term>$g_global_settings</term>
<listitem>
<para>This option contains the list of regular expressions that are used to determine if it is allowed for a specific configuraiton option to be saved to or loaded from the database. Configuration options that matches the regular expressions are considered global only and hence are only configurable via the config_inc.php file and defaulted by config_defaults_inc.php file.</para>
<para>This option contains the list of regular expressions that are used to determine if it is allowed for a specific configuration option to be saved to or loaded from the database. Configuration options that matches the regular expressions are considered global only and hence are only configurable via the config_inc.php file and defaulted by config_defaults_inc.php file.</para>
</listitem>
</varlistentry>
</variablelist>
Expand Down Expand Up @@ -500,7 +500,7 @@
<term>$g_smtp_host</term>
<listitem>
<para>This option specifies the SMTP server to submit messages to. The SMTP
server (MTA) then takes on the responsibility of deliverying such messages
server (MTA) then takes on the responsibility of delivering such messages
to their final destinations. To use the local SMTP (if available) set this
to 'localhost', otherwise use the fully qualified domain name of the remote
SMTP server. Default value is 'localhost'.
Expand Down Expand Up @@ -636,7 +636,7 @@
</para>
</listitem>
<listitem>
<para>the recipient has no email address extered</para>
<para>the recipient has no email address entered</para>
</listitem>
</itemizedlist>
</para>
Expand Down Expand Up @@ -849,7 +849,7 @@
<para>In view all bug page, show a clip icon next to bugs that has
one or more attachments. The default value is OFF.
The reason why this is defaulted to OFF is that it adds an extra
query for every bug dispayed in the list.
query for every bug displayed in the list.
</para>
</listitem>
</varlistentry>
Expand Down Expand Up @@ -880,7 +880,7 @@
<term>$g_show_realname</term>
<listitem>
<para>This control will replace the user's userid with their
realname. If it is set to ON, and the real name fiels has been
realname. If it is set to ON, and the real name field has been
populated, the replacement will occur. It defaults to OFF.
</para>
</listitem>
Expand Down Expand Up @@ -1320,10 +1320,10 @@
<varlistentry>
<term>$g_summary_category_include_project</term>
<listitem>
<para>Specifies whether category names should be preceeded by
<para>Specifies whether category names should be preceded by
project names (eg: [Project] Category) when the summary page is
viewed for all projects. This is useful in the case where category
names are common accross projects. The default is OFF.
names are common across projects. The default is OFF.
</para>
</listitem>
</varlistentry>
Expand Down Expand Up @@ -1444,7 +1444,7 @@
<varlistentry>
<term>$g_file_upload_method</term>
<listitem>
<para>Specify the location for uploading attachements. This can be
<para>Specify the location for uploading attachments. This can be
DISK, DATABASE, or FTP. In case of FTP, the files are saved on the
webserver (same as disk) as well as on the specified FTP server.
Default value is DATABASE.
Expand Down Expand Up @@ -1485,7 +1485,7 @@
<varlistentry>
<term>$g_file_upload_ftp_pass</term>
<listitem>
<para>Password to use when loggin in to the FTP server.</para>
<para>Password to use when logging in to the FTP server.</para>
</listitem>
</varlistentry>
<varlistentry>
Expand Down Expand Up @@ -1612,7 +1612,7 @@
<varlistentry>
<term>$g_bottom_include_page</term>
<listitem>
<para>If this page eixsts it will be displayed at the bottom of
<para>If this page exists it will be displayed at the bottom of
every page. It makes a good company branding include page.
</para>
</listitem>
Expand Down Expand Up @@ -2669,7 +2669,7 @@
<varlistentry>
<term>$$g_custom_field_edit_after_create</term>
<listitem>
<para>This flag determines whether to start editng a custom field
<para>This flag determines whether to start editing a custom field
immediately after creating it, or return to the definition list.
The default is ON (edit the custom field after creating).
</para>
Expand Down Expand Up @@ -3062,7 +3062,7 @@
<listitem>
<para>
An array of optional fields to show on the bug change
status page. This only changes the visibibility of
status page. This only changes the visibility of
fields shown below the form used for updating the
status of an issue.
</para>
Expand Down Expand Up @@ -3201,7 +3201,7 @@
<term>$g_time_tracking_stopwatch</term>
<listitem>
<para>
Instead of a text field turning this option on places a stopwatch on the page with <guibutton>Start/Stop</guibutton> and <guibutton>Reset</guibutton> buttons next to it. You must have $g_use_javascript switched on for this to take effect. A bit gimickie, but who cares.
Instead of a text field turning this option on places a stopwatch on the page with <guibutton>Start/Stop</guibutton> and <guibutton>Reset</guibutton> buttons next to it. You must have $g_use_javascript switched on for this to take effect. A bit gimmicky, but who cares.
</para>
</listitem>
</varlistentry>
Expand All @@ -3219,7 +3219,7 @@
<term>$g_time_tracking_edit_threshold</term>
<listitem>
<para>
Access level required to add/edit time tracking information (If you give a user $g_time_tracking_edit_threshold you must give them $g_time_tracking_view_threshold aswell) - Default DEVELOPER.
Access level required to add/edit time tracking information (If you give a user $g_time_tracking_edit_threshold you must give them $g_time_tracking_view_threshold as well) - Default DEVELOPER.
</para>
</listitem>
</varlistentry>
Expand Down
12 changes: 6 additions & 6 deletions docbook/Admin_Guide/en-US/Customizing.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -431,7 +431,7 @@ function custom_function_override_enum_mine() {
</para>

<para>Notice "override" in the function name. This is because this method is
defined by the MantisBT adminstrator/webmaster and not part of the MantisBT source.
defined by the MantisBT administrator/webmaster and not part of the MantisBT source.
It is OK to override a method that doesn't exist.</para>

<para>As usual, when MantisBT is upgraded to future releases, the custom functions
Expand Down Expand Up @@ -741,9 +741,9 @@ functions section.</para>
<title>Custom Functions</title>

<para>Custom functions are used to extend the functionality of
MantisBT by integrating user writtenfunctions into the issue
MantisBT by integrating user written functions into the issue
processing at strategic places. This allows the system
administrator to changethe functionality without re-writing parts
administrator to change the functionality without re-writing parts
of the internals of the code.
</para>
<para>User versions of these functions are
Expand All @@ -754,12 +754,12 @@ functions section.</para>
them instead of the provided default functions.</para>
<para>Custom functions have
names like custom_function_override_descriptive_name where
descriptive namedescribed the particular function. The specific
functions are described below. The simplest way tocreate a custom
descriptive name described the particular function. The specific
functions are described below. The simplest way to create a custom
function is to copy the default function, named
custom_function_default_descriptive_namefrom the
core/custom_function_api.php file to your override file
(custom_functions_inc.php), andrename it. The specific
(custom_functions_inc.php), and rename it. The specific
functionality you need can then be coded into the override
function.
</para>
Expand Down
22 changes: 11 additions & 11 deletions docbook/Admin_Guide/en-US/Installation.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@

<orderedlist>
<listitem>
<para>Tranfer files</para>
<para>Transfer files</para>
</listitem>
<listitem>
<para>Uncompress files</para>
Expand Down Expand Up @@ -68,7 +68,7 @@
<listitem>
<para>First, transfer the file to your webserver using whatever
method you likebest (ftp, scp, etc). You will need to telnet/ssh
into the server machine forthe next steps.
into the server machine for the next steps.
</para>
</listitem>
<listitem>
Expand All @@ -87,7 +87,7 @@
</listitem>
<listitem>
<para>Next we will create the necessary database tables and a
basic configurationfile.From your web server, access
basic configuration file. From your web server, access
http://yoursite/mantisbt/admin/install.php. This page will walk through
the following steps:

Expand Down Expand Up @@ -133,8 +133,8 @@
</listitem>
<listitem>
<para>The next part involves configuring the installation to
work with yourspecific setup.Open the file in an editor and add
anyother values that are required. There aremany more that you can
work with your specific setup. Open the file in an editor and add
any other values that are required. There are many more that you can
use to customize your MantisBT installation.
See <xref linkend="admin.config" /> for
in depth explanations.The file will overwrite the default values
Expand All @@ -143,16 +143,16 @@
NOTE: check.php sometimes reports the value of
register_globalsincorrectly.
Create a page with this line in it: &lt;? phpinfo() ?&gt;, save
itwith a .php extension and load it up in your web browser. It
will, among amultitude of other things, have the correct value of
register_globals that youare using.
it with a .php extension and load it up in your web browser. It
will, among a multitude of other things, have the correct value of
register_globals that you are using.
</para>
</listitem>

<listitem>
<para>MantisBT now uses only .php files.If your webserver is
configured for other extensions (.PHP3, .PHTML) then youwill have
to have the administrator add support for .PHP files. This shouldbe
configured for other extensions (.PHP3, .PHTML) then you will have
to have the administrator add support for .PHP files. This should be
a trivial modification.Documentation can be found at:
http://www.php.net/manual/en/installation.php
</para>
Expand Down Expand Up @@ -213,7 +213,7 @@

<itemizedlist>
<listitem>
<para>Mysqli or PostgreSQL or another vendor specific
<para>MySQL or PostgreSQL or another vendor specific
database extension that matches the type of database you
are using with MantisBT - mandatory.</para>
</listitem>
Expand Down
8 changes: 4 additions & 4 deletions docbook/Admin_Guide/en-US/Page_Descriptions.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
remain at the login page. An error message will be displayed.The
administrator may allow users to sign up for their own accounts. If
so, a link to Signup for your own account will be available.The
administrator may also have annonymous login allowed. Annonymous
administrator may also have anonymous login allowed. Anonymous
users will be logged in under a common account.You will be allowed
to select a project to work in after logging in. You can make a
project your default selection from the Select Project screen or
Expand Down Expand Up @@ -229,7 +229,7 @@

<title>Issue Edit page</title>

<para>The layout of this page resemples the Simple Issue View
<para>The layout of this page resembles the Simple Issue View
page, but here you can update various issue fields. The Reporter,
Category, Severity, and Reproducibility fields are editable but
shouldn't be unless there is a gross mis-categorization.Also
Expand Down Expand Up @@ -436,7 +436,7 @@
</para>
<para>
All fields are compared in length to be greater than or equal to
the minimum length, and less than or equal to the manimum length,
the minimum length, and less than or equal to the minimum length,
unless these values are 0. If the values are 0, the check is
skipped. All fields are also compared against the regular
expression. If the value matches the expression, then the value is
Expand Down Expand Up @@ -959,7 +959,7 @@
</para>
</listitem>
<listitem>
<para>the recipient has no email address extered</para>
<para>the recipient has no email address entered</para>
</listitem>
</itemizedlist>
The matrix on this page selects who will receive messages for each
Expand Down
6 changes: 3 additions & 3 deletions docbook/Admin_Guide/en-US/Project_Management.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ function custom_function_override_changelog_print_issue( $p_issue_id, $p_issue_l

<para>By combining both customization features, it is also possible to do more advanced customization scenarios. For example, users can add a 'ChangelogSummary' custom field and include all issues that have such field in the change log. Through customizing what information being included for a qualifying issue, users can also include the 'ChangelogSummary' text rather than the native summary field.</para>

<para>In some cases, users know that they fixed an issue and that the fix will be included in the next release, however, they don't know yet the name of the release. In such case, the recommended approach is to always have a version defined that corresponds to the next release, which is typicalled called 'Next Release'. Once the release is cut and has a concrete name, then 'Next Release' can be renamed to the appropriate name and a new 'Next Release' can then be created. For teams that manage releases from multiple branches for the same project, then more than one next release can be possible. For example, 'Next Dev Release' and 'Next Stable Release'.</para>
<para>In some cases, users know that they fixed an issue and that the fix will be included in the next release, however, they don't know yet the name of the release. In such case, the recommended approach is to always have a version defined that corresponds to the next release, which is typically called 'Next Release'. Once the release is cut and has a concrete name, then 'Next Release' can be renamed to the appropriate name and a new 'Next Release' can then be created. For teams that manage releases from multiple branches for the same project, then more than one next release can be possible. For example, 'Next Dev Release' and 'Next Stable Release'.</para>

<para>Another common requirement is to be able to link to the change log of a specific project from the project's main website. There is a variety of ways to do that:
<itemizedlist>
Expand All @@ -86,7 +86,7 @@ function custom_function_override_changelog_print_issue( $p_issue_id, $p_issue_l
</para>
</listitem>
<listitem>
<para>To link to the changelog of version with id 1. The version id is unique accross all projects and hence in this case it is not necessary to include the project id/name. The version id can be figured out by going to the manage project page and editing the required version. The version_id will be included in the URL.
<para>To link to the changelog of version with id 1. The version id is unique across all projects and hence in this case it is not necessary to include the project id/name. The version id can be figured out by going to the manage project page and editing the required version. The version_id will be included in the URL.
<programlisting>
http://www.example.com/mantisbt/changelog_page.php?version_id=1
</programlisting>
Expand Down Expand Up @@ -190,7 +190,7 @@ function custom_function_override_roadmap_print_issue( $p_issue_id, $p_issue_lev
</para>
</listitem>
<listitem>
<para>To link to the roadmap of version with id 1. The version id is unique accross all projects and hence in this case it is not necessary to include the project id/name. The version id can be figured out by going to the manage project page and editing the required version. The version_id will be included in the URL.
<para>To link to the roadmap of version with id 1. The version id is unique across all projects and hence in this case it is not necessary to include the project id/name. The version id can be figured out by going to the manage project page and editing the required version. The version_id will be included in the URL.
<programlisting>
http://www.example.com/mantisbt/roadmap_page.php?version_id=1
</programlisting>
Expand Down
4 changes: 2 additions & 2 deletions docbook/Admin_Guide/en-US/User_Management.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,7 @@

<para>The pruning function allows deleting of user accounts for accounts
that have been created more than a week ago, and they never logged in.
This is particulary useful for users who signed up with an invalid email
This is particularly useful for users who signed up with an invalid email
or with a typo in their email address address.</para>

<para>The account pruning can be done by administrators by going to
Expand Down Expand Up @@ -237,7 +237,7 @@
access levels. For example, a user may have REPORTER as the global
access level, but have a MANAGER access level to a specific project. Or
a user may have MANAGER as the global access level by VIEWER access to
a specific project. Access levels can be overriden for both public and
a specific project. Access levels can be overridden for both public and
private projects. However, overriding access level is not allowed for
users with global access ADMINISTRATOR.</para>

Expand Down
Loading

0 comments on commit 3081622

Please sign in to comment.