[Jifty-commit] jifty branch, master, updated. 17b4e79fe1ff7384c411d7fd86c4ce950f7866a6
Jifty commits
jifty-commit at lists.jifty.org
Wed Dec 8 18:32:41 EST 2010
The branch, master has been updated
via 17b4e79fe1ff7384c411d7fd86c4ce950f7866a6 (commit)
via 075ee70cc5f1397a9e7661bb7bea9323b6a05d44 (commit)
from 45c298995b6088b3ec69f4a8486c4a56e9e664e5 (commit)
Summary of changes:
lib/Jifty.pm | 12 +-
lib/Jifty/Action.pm | 8 +-
lib/Jifty/Action/Autocomplete.pm | 2 +-
lib/Jifty/Action/Record.pm | 2 +-
lib/Jifty/Action/Redirect.pm | 2 +-
lib/Jifty/CAS/Blob.pm | 2 +-
lib/Jifty/ClassLoader.pm | 4 +-
lib/Jifty/Config.pm | 8 +-
lib/Jifty/Continuation.pm | 2 +-
lib/Jifty/DateTime.pm | 4 +-
lib/Jifty/Dispatcher.pm | 8 +-
lib/Jifty/Event.pm | 2 +-
lib/Jifty/Event/Log.pm | 2 +-
lib/Jifty/Event/Model.pm | 2 +-
lib/Jifty/Everything.pm | 2 +-
lib/Jifty/Handler.pm | 2 +-
lib/Jifty/JSON.pm | 8 +-
lib/Jifty/LetMe.pm | 10 +-
lib/Jifty/Logger.pm | 8 +-
lib/Jifty/Manual/AccessControl.pod | 2 +-
lib/Jifty/Manual/Actions.pod | 4 +-
lib/Jifty/Manual/Actions_zhtw.pod | 6 +-
lib/Jifty/Manual/Continuations.pod | 2 +-
lib/Jifty/Manual/Cookbook.pod | 26 +-
lib/Jifty/Manual/Deploying.pod | 12 +-
lib/Jifty/Manual/Deploying_zhtw.pod | 12 +-
lib/Jifty/Manual/FAQ.pod | 2 +-
lib/Jifty/Manual/Glossary.pod | 2 +-
lib/Jifty/Manual/JavaScript.pod | 28 +-
lib/Jifty/Manual/JavaScript_zhtw.pod | 28 +-
lib/Jifty/Manual/Logging.pod | 2 +-
lib/Jifty/Manual/Models.pod | 10 +-
lib/Jifty/Manual/ObjectModel.pod | 6 +-
lib/Jifty/Manual/PageRegions.pod | 6 +-
lib/Jifty/Manual/RequestHandling.pod | 6 +-
lib/Jifty/Manual/Style.pod | 2 +-
lib/Jifty/Manual/Tutorial.pod | 2 +-
lib/Jifty/Manual/jQueryMigrationGuide.pod | 4 +-
lib/Jifty/Model/Metadata.pm | 2 +-
lib/Jifty/Module/Pluggable.pm | 2 +-
lib/Jifty/Plugin.pm | 2 +-
.../ActorMetadata/Mixin/Model/ActorMetadata.pm | 2 +-
.../Password/Action/ResetLostPassword.pm | 2 +-
.../Plugin/Authentication/Password/Dispatcher.pm | 16 +-
.../Authentication/Password/Mixin/Model/User.pm | 2 +-
lib/Jifty/Plugin/CSSQuery.pm | 4 +-
lib/Jifty/Plugin/ClassLoader.pm | 4 +-
lib/Jifty/Plugin/Compat.pm | 2 +-
lib/Jifty/Plugin/Config.pm | 2 +-
lib/Jifty/Plugin/Deflater.pm | 2 +-
lib/Jifty/Plugin/ErrorTemplates/View.pm | 2 +-
lib/Jifty/Plugin/Halo.pm | 4 +-
lib/Jifty/Plugin/I18N.pm | 2 +-
lib/Jifty/Plugin/IEFixes.pm | 2 +-
lib/Jifty/Plugin/LetMe.pm | 2 +-
lib/Jifty/Plugin/REST.pm | 4 +-
lib/Jifty/Plugin/REST/Dispatcher.pm | 12 +-
lib/Jifty/Plugin/RequestInspector.pm | 2 +-
lib/Jifty/Plugin/SQLQueries.pm | 2 +-
lib/Jifty/Plugin/TestServerWarnings/View.pm | 2 +-
lib/Jifty/Plugin/ViewDeclarePage/Page.pm | 10 +-
lib/Jifty/Record.pm | 8 +-
lib/Jifty/Request.pm | 10 +-
lib/Jifty/Request/Mapper.pm | 4 +-
lib/Jifty/Schema.pm | 8 +-
lib/Jifty/Script.pm | 4 +-
lib/Jifty/Script/FastCGI.pm | 4 +-
lib/Jifty/Script/Po.pm | 4 +-
lib/Jifty/Script/Schema.pm | 4 +-
lib/Jifty/Script/Server.pm | 2 +-
lib/Jifty/Subs/Render.pm | 2 +-
lib/Jifty/Test/WWW/Mechanize.pm | 2 +-
lib/Jifty/Upgrade.pm | 4 +-
lib/Jifty/Upgrade/Internal.pm | 2 +-
lib/Jifty/Util.pm | 4 +-
lib/Jifty/View/Declare/CRUD.pm | 6 +-
lib/Jifty/View/Declare/CoreTemplates.pm | 2 +-
lib/Jifty/View/Mason/Handler.pm | 4 +-
lib/Jifty/Web.pm | 8 +-
lib/Jifty/Web/Form.pm | 2 +-
lib/Jifty/Web/Form/Clickable.pm | 8 +-
lib/Jifty/Web/Form/Element.pm | 2 +-
lib/Jifty/Web/Form/Field.pm | 14 +-
lib/Jifty/Web/Form/Field/Date.pm | 4 +-
lib/Jifty/Web/Form/Field/Upload.pm | 2 +-
lib/Jifty/Web/Form/Field/Uploads.pm | 2 +-
lib/Jifty/Web/Menu.pm | 2 +-
lib/Jifty/Web/PageRegion.pm | 4 +-
lib/Jifty/Web/Session.pm | 2 +-
lib/Jifty/Web/Session/JDBI.pm | 2 +-
share/web/static/js/jifty.js | 4 +-
share/web/static/js/jquery-1.4.1.js | 2 +-
.../web/templates/__jifty/error/_elements/wrapper | 2 +-
share/web/templates/__jifty/error/error.css | 2 +-
t/99-pod-spelling.t | 397 ++++++++++++++++++++
.../lib/TestApp/Plugin/SetupWizard/Test.pm | 2 +-
96 files changed, 636 insertions(+), 237 deletions(-)
create mode 100644 t/99-pod-spelling.t
- Log -----------------------------------------------------------------
commit 075ee70cc5f1397a9e7661bb7bea9323b6a05d44
Author: Shawn M Moore <sartak at bestpractical.com>
Date: Wed Dec 8 18:29:28 2010 -0500
Spellcheck!
diff --git a/lib/Jifty.pm b/lib/Jifty.pm
index 477ac74..566c2c2 100644
--- a/lib/Jifty.pm
+++ b/lib/Jifty.pm
@@ -136,7 +136,7 @@ handle to exist. Defaults to false.
The name that Jifty::Logger will log under. If you don't specify anything
Jifty::Logger will log under the empty string. See L<Jifty::Logger> for
-more infomation.
+more information.
=back
@@ -153,7 +153,7 @@ sub new {
@_
);
- # Add the appliation's library path
+ # Add the application's library path
push @INC, File::Spec->catdir(Jifty::Util->app_root, "lib");
# Now that we've loaded the configuration, we can remove the temporary
@@ -459,7 +459,7 @@ sub class_loader {
=head2 setup_database_connection
-Set up our database connection. Optionally takes a param hash with a
+Set up our database connection. Optionally takes a paramhash with a
single argument. This method is automatically called by L</new>.
=over
@@ -470,9 +470,9 @@ Defaults to false. If true, Jifty won't try to set up a database handle
=item pre_init
-Defaults to false. If true, plugins are notificed that this is a
+Defaults to false. If true, plugins are notified that this is a
pre-init, any trigger registration in C<init()> should not happen
-during this stage. Note that model mixins's register_triggers is
+during this stage. Note that model mixins' C<register_triggers> is
unrelated to this.
=back
@@ -494,7 +494,7 @@ sub setup_database_connection {
or not Jifty->config->framework('Database') )
{
- # Load the app's database handle and connect
+ # Load the application's database handle and connect
my $handle_class = Jifty->app_class("Handle");
Jifty::Util->require( $handle_class );
Jifty->handle( $handle_class->new );
diff --git a/lib/Jifty/Action.pm b/lib/Jifty/Action.pm
index 499a9a2..8a900ab 100644
--- a/lib/Jifty/Action.pm
+++ b/lib/Jifty/Action.pm
@@ -125,7 +125,7 @@ sub new {
# XXX Should this be pickier about sanitized monikers?
- # Monkiers must not contain semi-colons
+ # Monikers must not contain semi-colons
if ( $args{'moniker'} =~ /[\;]/ ) {
# Replace the semis with underscores and warn
@@ -1067,7 +1067,7 @@ sub _autocomplete_argument {
Given an L<parameter|Jifty::Manual::Glossary/parameter> name, returns the
list of valid values for it, based on its C<valid_values> field.
-This method returns a hash referenece with a C<display> field for the string
+This method returns a hash reference with a C<display> field for the string
to display for the value, and a C<value> field for the value to actually send
to the server.
@@ -1141,7 +1141,7 @@ sub _values_for_field {
# Check for a collection spec
if ( $v->{'collection'} ) {
- # Load the display_from/value_from paramters
+ # Load the display_from/value_from parameters
my $disp = $v->{'display_from'};
my $val = $v->{'value_from'};
@@ -1305,7 +1305,7 @@ sub deny {
=head2 Canonicalization
If you wish to have the data in a field normalized into a particular
-format (such as changing a date into YYYY-MM-DD format, adding commas
+format (such as changing a date into C<YYYY-MM-DD> format, adding commas
to numbers, capitalizing words, or whatever you need) you can do so
using a canonicalizer.
diff --git a/lib/Jifty/Action/Autocomplete.pm b/lib/Jifty/Action/Autocomplete.pm
index b90ece6..222498a 100644
--- a/lib/Jifty/Action/Autocomplete.pm
+++ b/lib/Jifty/Action/Autocomplete.pm
@@ -51,7 +51,7 @@ sub arguments {
=head2 take_action
Find the submitted action in the L<Jifty::Request> named by the
-C<action> above, and ask it for autocompletion possibilites for the
+C<action> above, and ask it for autocompletion possibilities for the
L<argument> in question.
=cut
diff --git a/lib/Jifty/Action/Record.pm b/lib/Jifty/Action/Record.pm
index e0cc3ba..c3894eb 100644
--- a/lib/Jifty/Action/Record.pm
+++ b/lib/Jifty/Action/Record.pm
@@ -79,7 +79,7 @@ Construct a new C<Jifty::Action::Record> (as mentioned in
L<Jifty::Action>, this should only be called by C<<
framework->new_action >>. The C<record> value, if provided in the
PARAMHASH, will be used to load the L</record>; otherwise, the
-parimary keys will be loaded from the action's argument values, and
+primary keys will be loaded from the action's argument values, and
the L</record> loaded from those primary keys.
=cut
diff --git a/lib/Jifty/Action/Redirect.pm b/lib/Jifty/Action/Redirect.pm
index 653d0a1..8f52ab7 100644
--- a/lib/Jifty/Action/Redirect.pm
+++ b/lib/Jifty/Action/Redirect.pm
@@ -16,7 +16,7 @@ Jifty::Action::Redirect - Redirect the browser
=head1 DESCRIPTION
-Given a URL, this action forces Jifty to perform a redirect to thast URL after processing the rest of the request.
+Given a URL, this action forces Jifty to perform a redirect to that URL after processing the rest of the request.
=cut
diff --git a/lib/Jifty/CAS/Blob.pm b/lib/Jifty/CAS/Blob.pm
index 41f3902..2caa8be 100644
--- a/lib/Jifty/CAS/Blob.pm
+++ b/lib/Jifty/CAS/Blob.pm
@@ -47,7 +47,7 @@ Returns a hashref of metadata.
=head2 key
-Retuens the key calculated for this content.
+Returns the key calculated for this content.
=cut
diff --git a/lib/Jifty/ClassLoader.pm b/lib/Jifty/ClassLoader.pm
index 069b3a9..98de5db 100644
--- a/lib/Jifty/ClassLoader.pm
+++ b/lib/Jifty/ClassLoader.pm
@@ -65,7 +65,7 @@ or just about anything else.
=item I<Application>
-An empty application base class is created that doen't provide any
+An empty application base class is created that doesn't provide any
methods or inherit from anything.
=item I<Application>::Action
@@ -412,7 +412,7 @@ line of code(*).
working on it.
This method finds all database-backed models and instantiates jifty classes for
-them it returns a list of classnames of the models it created.
+them it returns a list of class names of the models it created.
=cut
diff --git a/lib/Jifty/Config.pm b/lib/Jifty/Config.pm
index 0613c49..d4259d4 100644
--- a/lib/Jifty/Config.pm
+++ b/lib/Jifty/Config.pm
@@ -197,7 +197,7 @@ assumed based on the name of the application -- see L</guess>.
=head3 Reblessing into application's sub-class
-Ok, config is ready. Rebless this object into C<YourApp::Config> class
+OK, config is ready. Rebless this object into C<YourApp::Config> class
and call L</post_load> hook, so you can do some tricks detailed in
L</SUB-CLASSING>.
@@ -664,7 +664,7 @@ For example check if file or module exists.
=item * canonicalization
For example turn relative paths into absolute or translate all possible
-variants of an option to a canonic structure
+variants of an option into a canonical structure
=item * generation
@@ -687,7 +687,7 @@ Sub-classing is definitely not for:
You have L<so many files|/"WHY SO MANY FILES"> to allow users of your
app and you to override defaults.
-=item * anything else, but configs
+=item * anything else but configuration
=back
@@ -711,7 +711,7 @@ This provides an additional layer of abstraction for truly complicated deploymen
=head2 SITE
-The site configuration allows for specific overrides of the application and vendor configuration. For example, a particular Jifty application might define all the application defaults in the application configuration file. Then, each administrator that has downloaded that appliation and is installing it locally might customize the configuration for a particular deployment using this configuration file, while leaving the application defaults intact (and, thus, still available for later reference). This can even override the vendor file containing a standard set of overrides.
+The site configuration allows for specific overrides of the application and vendor configuration. For example, a particular Jifty application might define all the application defaults in the application configuration file. Then, each administrator that has downloaded that application and is installing it locally might customize the configuration for a particular deployment using this configuration file, while leaving the application defaults intact (and, thus, still available for later reference). This can even override the vendor file containing a standard set of overrides.
=head1 SEE ALSO
diff --git a/lib/Jifty/Continuation.pm b/lib/Jifty/Continuation.pm
index 41bb436..0192d8f 100644
--- a/lib/Jifty/Continuation.pm
+++ b/lib/Jifty/Continuation.pm
@@ -237,7 +237,7 @@ sub call {
Returns from the continuation by pulling out the stored request, and
setting that to be the active request. This shouldn't need to be
called by hand -- use L<Jifty::Request/return_from_continuation>,
-which ensures that all requirements are ment before it calls this.
+which ensures that all requirements are met before it calls this.
=cut
diff --git a/lib/Jifty/DateTime.pm b/lib/Jifty/DateTime.pm
index 8184b28..28ef428 100644
--- a/lib/Jifty/DateTime.pm
+++ b/lib/Jifty/DateTime.pm
@@ -278,7 +278,7 @@ sub new_from_string {
# Hack to use Date::Manip to flexibly scan dates from strings
{
- # Date::Manip interprets days of the week (eg, ''monday'') as
+ # Date::Manip interprets days of the week (eg, ''Monday'') as
# days within the *current* week. Detect these and prepend
# ``next''
# XXX TODO: Find a real solution (better date-parsing library?)
@@ -324,7 +324,7 @@ sub new_from_string {
Returns the date given by this C<Jifty::DateTime> object. It will display "today"
for today, "tomorrow" for tomorrow, or "yesterday" for yesterday. Any other date
-will be displayed in ymd format.
+will be displayed in C<ymd> format.
We currently shift by "24 hours" to detect yesterday and tomorrow, rather than
"1 day" because of daylight saving issues. "1 day" can result in invalid local
diff --git a/lib/Jifty/Dispatcher.pm b/lib/Jifty/Dispatcher.pm
index 5f6d1d4..e986123 100644
--- a/lib/Jifty/Dispatcher.pm
+++ b/lib/Jifty/Dispatcher.pm
@@ -130,8 +130,8 @@ that is, given a C<before plugin qr/^Jifty::Plugin::Auth::/> and both
a C<Jifty::Plugin::Auth::Basic> and a C<Jifty::Plugin::Auth::Complex>,
the rules will be placed before the first.
-C<after app> inserts the folowing C<RULES> after the application's
-dispatcher rules, and is identical to, but hopefuly clearer than,
+C<after app> inserts the following C<RULES> after the application's
+dispatcher rules, and is identical to, but hopefully clearer than,
C<< after plugin Jifty => RULES >>.
C<RULES> may either be a single C<before>, C<on>, C<under>, or
@@ -754,7 +754,7 @@ sub _do_tangent {
=head2 _do_stream CODE
-THe method is called by the dispatcher internally. You shouldn't need to.
+The method is called by the dispatcher internally. You shouldn't need to.
Take a coderef that returns a PSGI streamy response code.
@@ -918,7 +918,7 @@ as the first match is found.
Hashref conditions are conjunctions: each non-empty hash key triggers a
separate C<_match_$keyname> call on the dispatcher object. For example, a
C<method> key would call C<_match_method> with its value to be matched against.
-After each subcondition is tried (in lexographical order) and succeeded,
+After each subcondition is tried (in lexicographical order) and succeeded,
the value associated with the C<''> key is matched again as the condition.
=cut
diff --git a/lib/Jifty/Event.pm b/lib/Jifty/Event.pm
index 0800d40..3d2282e 100644
--- a/lib/Jifty/Event.pm
+++ b/lib/Jifty/Event.pm
@@ -91,7 +91,7 @@ sub republish {
=head2 encode_queries(@query)
-Encode queries into some sort of canonical md5 encoding.
+Encode queries into some sort of canonical MD5 encoding.
=cut
diff --git a/lib/Jifty/Event/Log.pm b/lib/Jifty/Event/Log.pm
index 9722d80..0bbe053 100644
--- a/lib/Jifty/Event/Log.pm
+++ b/lib/Jifty/Event/Log.pm
@@ -33,7 +33,7 @@ sub match {
=head2 render_arguments
-All of the data is dumped into the redered arguments, verbatim.
+All of the data is dumped into the rendered arguments, verbatim.
=cut
diff --git a/lib/Jifty/Event/Model.pm b/lib/Jifty/Event/Model.pm
index 00f5860..eca797d 100644
--- a/lib/Jifty/Event/Model.pm
+++ b/lib/Jifty/Event/Model.pm
@@ -24,7 +24,7 @@ As yet, this functionality is unused.
=head2 new
creates a new L<Jifty::Event::Model> object. If C<PubSub> is enabled for your application,
-checks to make sure that this event has the following (underdocumented) parameters:
+checks to make sure that this event has the following (under-documented) parameters:
record_id record_class action_class action_arguments timestamp result as_hash_before as_hash_after current_user_id
diff --git a/lib/Jifty/Everything.pm b/lib/Jifty/Everything.pm
index 292f1eb..4df8336 100644
--- a/lib/Jifty/Everything.pm
+++ b/lib/Jifty/Everything.pm
@@ -9,7 +9,7 @@ Jifty::Everything - Load all of the important Jifty modules at once.
=head1 DESCRIPTION
-This package is loaded very early in the processof loading Jifty to bring in all of the wonderful goodies that make up Jifty. If you use L<JIfty>:
+This package is loaded very early in the process of loading Jifty to bring in all of the wonderful goodies that make up Jifty. If you use L<JIfty>:
use Jifty;
diff --git a/lib/Jifty/Handler.pm b/lib/Jifty/Handler.pm
index 449a8c1..09bcd45 100644
--- a/lib/Jifty/Handler.pm
+++ b/lib/Jifty/Handler.pm
@@ -202,7 +202,7 @@ sub psgi_app {
=head2 handle_request
-When your server processs (be it Jifty-internal, FastCGI or anything
+When your server process (be it Jifty-internal, FastCGI or anything
else) wants to handle a request coming in from the outside world, you
should call C<handle_request>.
diff --git a/lib/Jifty/JSON.pm b/lib/Jifty/JSON.pm
index 711b0b3..b128cd8 100644
--- a/lib/Jifty/JSON.pm
+++ b/lib/Jifty/JSON.pm
@@ -26,7 +26,7 @@ Provides a thin wrapper around the L<JSON> 2.xx library, which provides a
frontend for L<JSON::XS> and L<JSON::PP>.
This module used to wrap L<JSON::Syck> and L<JSON> 1.xx with special-casing for
-outputing JSON with single quoted values. Single quotes make it easy to
+outputting JSON with single quoted values. Single quotes make it easy to
simply plop JSON into HTML attributes but are in violation of the JSON spec
which mandates only double quoted strings.
@@ -66,9 +66,11 @@ sub encode_json {
JSON::to_json( $_[0], { utf8 => 1, allow_nonref => 1, %{$_[1] || {}} } );
}
-=head2 DEPRECATED jsonToObj JSON, [ARGUMENTS]
+=head1 DEPRECATED FUNCTIONS
-=head2 DEPRECATED objToJson JSON, [ARGUMENTS]
+=head2 jsonToObj JSON, [ARGUMENTS]
+
+=head2 objToJson JSON, [ARGUMENTS]
These functions are deprecated and provided for backwards compatibility. They
wrap the appropriate function above, but L<Carp/croak> if you try to set the
diff --git a/lib/Jifty/LetMe.pm b/lib/Jifty/LetMe.pm
index b755fb7..7ea076e 100644
--- a/lib/Jifty/LetMe.pm
+++ b/lib/Jifty/LetMe.pm
@@ -20,7 +20,7 @@ Create a new "LetMe" authentication object; it takes no parameters.
It calls L</_init> to do any initialization.
A LetMe is a way to provide a one-time-use URL for a particular purpose.
-All LetMe objects give you a way to validate someone's identity and to
+All LetMe objects give you a way to validate a user's identity and to
allow them a very small set of possible actions or page-access permissions.
For example, you can put a LetMe URL in an email to a new user,
@@ -111,7 +111,7 @@ sub _generate_digest {
=head2 generate_checksum
-Returns an auth checksum for the current combination of
+Returns an authentication checksum for the current combination of:
user
path
@@ -128,9 +128,9 @@ sub generate_checksum {
=head2 generate_koremutake_checksum
-Generate a slightly more pronouncable version of the checksum using
+Generate a slightly more pronounceable version of the checksum using
L<String::Koremutake>. Due to hex -> integer limitations, this is
-imporecise and may vary depending on the platform it is used on; as
+imprecise and may vary depending on the platform it is used on; as
such, it is deprecated.
=cut
@@ -261,7 +261,7 @@ sub base_path {
=head2 validate
-Returns true if the credentials the user presented validate ok.
+Returns true if the credentials the user presented validate OK.
Returns false otherwise.
=cut
diff --git a/lib/Jifty/Logger.pm b/lib/Jifty/Logger.pm
index 805b6e2..53f3292 100644
--- a/lib/Jifty/Logger.pm
+++ b/lib/Jifty/Logger.pm
@@ -13,7 +13,7 @@ Jifty uses the Log4perl module to log error messages. In Jifty
programs there's two ways you can get something logged:
Firstly, Jifty::Logger captures all standard warnings that Perl
-emits. So in addition to everying output from perl via the
+emits. So in addition to everything output from perl via the
warnings pragmas, you can also log messages like so:
warn("The WHAM is overheating!");
@@ -34,7 +34,7 @@ Unless you specify otherwise in the configuration file, Jifty will
supply a default Log4perl configuration.
The default log configuration that logs all messages to the screen
-(i.e. to STDERR, be that directly to the terminal or to fastcgi's
+(i.e. to STDERR, be that directly to the terminal or to the FastCGI
log file.) It will log all messages of equal or higher priority
to the LogLevel configuration option.
@@ -54,7 +54,7 @@ the format of this config file.)
Note that specifying your own config file prevents the LogLevel
config option from having any effect.
-You can tell Log4perl to check that file perodically for changes.
+You can tell Log4perl to check that file periodically for changes.
This costs you a little in application performance, but allows
you to change the logging level of a running application. You
need to set LogReload to the frequency, in seconds, that the
@@ -111,7 +111,7 @@ sub new {
# This caller_depth line tells Log4perl to report
# the error as coming from on step further up the
- # caller chain (ie, where the warning originated)
+ # caller chain (i.e., where the warning originated)
# instead of from the $logger->warn line.
local $Log::Log4perl::caller_depth = $Log::Log4perl::caller_depth + 1;
diff --git a/lib/Jifty/Manual/AccessControl.pod b/lib/Jifty/Manual/AccessControl.pod
index 321572e..7313d93 100644
--- a/lib/Jifty/Manual/AccessControl.pod
+++ b/lib/Jifty/Manual/AccessControl.pod
@@ -174,7 +174,7 @@ is called in the mail and results in accepting the user.
=item F</let/reset_lost_password>
-enabled by the passwordreminder template, this template allows a user
+enabled by the F</passwordreminder> template, this template allows a user
to reenter a password for future use.
=back
diff --git a/lib/Jifty/Manual/Actions.pod b/lib/Jifty/Manual/Actions.pod
index c191b05..9d35559 100644
--- a/lib/Jifty/Manual/Actions.pod
+++ b/lib/Jifty/Manual/Actions.pod
@@ -277,7 +277,7 @@ where C<'post_blog'> is the moniker for your post page action object.
In fact, that's exactly how actions "return" values to other components
in your application.
-Mutiple action "return values" are possible and arbitrary data structures
+Multiple action "return values" are possible and arbitrary data structures
can be passed too:
$self->result->content( keys => $keys );
@@ -386,7 +386,7 @@ of changes to many records at once.
=head1 ACTIONS AS WEB SERVICES
Your actions are also automatically published as web services.
-Clients can POST requsets, usually using the YAML or JSON request
+Clients can POST requests, usually using the YAML or JSON request
format. See C<bin/service> for a trivial generic webservice client.
(XXX TODO More about webservices)
diff --git a/lib/Jifty/Manual/Actions_zhtw.pod b/lib/Jifty/Manual/Actions_zhtw.pod
index 00afa5c..8a3a7d4 100644
--- a/lib/Jifty/Manual/Actions_zhtw.pod
+++ b/lib/Jifty/Manual/Actions_zhtw.pod
@@ -4,7 +4,7 @@ Jifty::Manual::Actions - 讓 Jifty åšäº‹
=head1 DESCRIPTION
-C<Jifty::Action> 抽象敘述了於編è¯æ™‚期 (complie time) 宣告åƒæ•¸çš„想法
+C<Jifty::Action> 抽象敘述了於編è¯æ™‚期 (compile time) 宣告åƒæ•¸çš„想法
(L<"parameters"|Jifty::Manual::Glossary/parameter>).
在執行時期 (runtime)，動作 (Action) 會收集使用者輸入資料åšç‚ºåƒæ•¸
@@ -268,7 +268,7 @@ where C<'post_blog'> is the moniker for your post page action object.
In fact, that's exactly how actions "return" values to other components
in your application.
-Mutiple action "return values" are possible and arbitrary data structures
+Multiple action "return values" are possible and arbitrary data structures
can be passed too:
$self->result->content( keys => $keys );
@@ -377,7 +377,7 @@ of changes to many records at once.
=head1 ACTIONS AS WEB SERVICES
Your actions are also automatically published as web services.
-Clients can POST requsets, usually using the YAML or JSON request
+Clients can POST requests, usually using the YAML or JSON request
format. See C<bin/service> for a trivial generic webservice client.
(XXX TODO More about webservices)
diff --git a/lib/Jifty/Manual/Continuations.pod b/lib/Jifty/Manual/Continuations.pod
index a8c7504..e102fe8 100644
--- a/lib/Jifty/Manual/Continuations.pod
+++ b/lib/Jifty/Manual/Continuations.pod
@@ -52,7 +52,7 @@ the user navigate between multiple pages before returning to the previous page:
Because this C<return> does not carry a result value, you can think of
it as a form of C<gosub>. In comparison, ordinary hyperlinks are akin to
-C<goto> staements.
+C<goto> statements.
Sometimes, it may be possible for the user to get to a location
without having a continuation set. In that case, clicking on the
diff --git a/lib/Jifty/Manual/Cookbook.pod b/lib/Jifty/Manual/Cookbook.pod
index 38b6fd1..fd756ef 100644
--- a/lib/Jifty/Manual/Cookbook.pod
+++ b/lib/Jifty/Manual/Cookbook.pod
@@ -55,7 +55,7 @@ to catch the file , in your C<take_action> method:
}
-=head2 Use PostgreSQL insteads of default SQLite database.
+=head2 Use PostgreSQL instead of the default SQLite database.
You need to modify your F<etc/config.yml> file.
@@ -199,11 +199,11 @@ like this:
This approach is not really accurate, if you render this field in a
form, then the defer value is evaluated by the time of rendering,
-which might be way eariler then the creation of record. However, it is
+which might be way earlier then the creation of record. However, it is
the easiest one.
-If you're using the newly recommeded C<JIfty::DBI::Record schema {}>
-to declare schemas, you might find this trick not working at the moment.
+If you're using the newly recommended C<JIfty::DBI::Record schema {}>
+to declare your schema, you might find this trick not working at the moment.
Please override model's C<before_create> method instead:
sub before_create {
@@ -254,12 +254,12 @@ Finally, you can also allow or deny specific actions in the
dispatcher, to limit who is able to perform what actions -- see
L<Jifty::API>.
-=head2 Run my Jifty app as fastcgi in Apache/Lighttpd ?
+=head2 Run my Jifty app as FastCGI in Apache/Lighttpd ?
-Jifty provides a really simple way to run the application as a fastcgi
-server. The complete instructions and examples are in C<'jifty help
-fastcgi'> for both Apache servers and Lighttpd servers. (Please C<cd> to
-your app dir before running this command.)
+Jifty provides a really simple way to run the application as a FastCGI
+server. The complete instructions and examples are in
+C<jifty help FastCGI> for both Apache servers and Lighttpd servers.
+(Please C<cd> to your app directory before running this command.)
You'll have to install C<CGI::Fast> and C<FCGI> module for this.
@@ -351,9 +351,9 @@ field is changed.
$self->argument_value( other_field => "new value" )
-=head2 Use iepngfix.htc to add PNG support in IE5.5+
+=head2 Use F<iepngfix.htc> to add PNG support in IE5.5+
-Jifty has included iepngfix.htc by Angus Turnbull. The HTC file will
+Jifty has included F<iepngfix.htc> by Angus Turnbull. The HTC file will
automatically add PNG support to IMG elements and also supports any
element with a "background-image" CSS property.
@@ -522,7 +522,7 @@ Document how to do this with Mason
=head2 Show login box on an action submit
-In app's dispatcher add the following:
+In your application's dispatcher add the following:
before '*' => run {
# do nothing if user is logged in
@@ -608,7 +608,7 @@ Last, but not least, you need to send arguments to the URL related to the action
id => { result_of => $create, name => 'id' },
-This line tells Jifty that you want to set the "id" paramter sent to the URL given in C<append>, to the "id" set when C<$create> is executed. That is, after running the action, Jifty will contact the URL and effectively perform:
+This line tells Jifty that you want to set the "id" parameter sent to the URL given in C<append>, to the "id" set when C<$create> is executed. That is, after running the action, Jifty will contact the URL and effectively perform:
set id => $create->result->content('id');
diff --git a/lib/Jifty/Manual/Deploying.pod b/lib/Jifty/Manual/Deploying.pod
index c665d59..608f8ac 100644
--- a/lib/Jifty/Manual/Deploying.pod
+++ b/lib/Jifty/Manual/Deploying.pod
@@ -167,7 +167,7 @@ You may want to adjust the configuration of the mailer you are using. See L<Jift
=item Plugins
-You may want to disable plugins you've been using in your development that you don't ened in production. In general, if these plugins are well-behaved this isn't necessary, but you can provide yourself with extra insurance in case they are not.
+You may want to disable plugins you've been using in your development that you don't need in production. In general, if these plugins are well-behaved this isn't necessary, but you can provide yourself with extra insurance in case they are not.
You can disable them without removing them from the file by commenting them out using the Perl-style "#" comment mark.
@@ -189,7 +189,7 @@ If you want to improve the performance of your server, you may want your main we
Your application configuration may have additional changes that need to be made for your application to operate properly in a production environment.
-Make sure to check over all the settings to make sure they will work in your produciton environment to save yourself headaches later.
+Make sure to check over all the settings to make sure they will work in your production environment to save yourself headaches later.
=back
@@ -263,11 +263,11 @@ Once you have done all of the above, your application should be ready to use at
=head2 Updating the Production Server
-After you've made some collection of updates to your Jifty application, you'll then need to install those changes onto your server and prepr your application to use the changes.
+After you've made some collection of updates to your Jifty application, you'll then need to install those changes onto your server and prepare your application to use the changes.
This documentation assumes a "cold" upgrade with the application offline during the duration of the process. A future version of this document might also include instructions for performing a "hot" upgrade without taking the server offline.
-You can do his with the following steps:
+You can do this with the following steps:
=over
@@ -309,7 +309,7 @@ Remember, shutdown all Jifty application processes before continuing, or bad thi
=head4 Shutting Down the Server
-This will involve a two step process. First, you will want to shutodwn your web server. The second is to shutdown the Jifty server. If you are using the built-in Jifty server, you may do this by running:
+This will involve a two step process. First, you will want to shutdown your web server. The second is to shutdown the Jifty server. If you are using the built-in Jifty server, you may do this by running:
bin/jifty server --stop
@@ -376,7 +376,7 @@ Again, you need to look for any configuration updates that need to adjusted. Thi
=head3 Clear Temporary/Cached Files
-This step is important to prevent strange issues from occuring. You remove all files from the following directories:
+This step is important to prevent strange issues from occurring. You remove all files from the following directories:
=over
diff --git a/lib/Jifty/Manual/Deploying_zhtw.pod b/lib/Jifty/Manual/Deploying_zhtw.pod
index 90ff5a4..e7488b8 100644
--- a/lib/Jifty/Manual/Deploying_zhtw.pod
+++ b/lib/Jifty/Manual/Deploying_zhtw.pod
@@ -173,7 +173,7 @@ You may want to adjust the configuration of the mailer you are using. See L<Jift
=item Plugins
-You may want to disable plugins you've been using in your development that you don't ened in production. In general, if these plugins are well-behaved this isn't necessary, but you can provide yourself with extra insurance in case they are not.
+You may want to disable plugins you've been using in your development that you don't need in production. In general, if these plugins are well-behaved this isn't necessary, but you can provide yourself with extra insurance in case they are not.
You can disable them without removing them from the file by commenting them out using the Perl-style "#" comment mark.
@@ -195,7 +195,7 @@ If you want to improve the performance of your server, you may want your main we
Your application configuration may have additional changes that need to be made for your application to operate properly in a production environment.
-Make sure to check over all the settings to make sure they will work in your produciton environment to save yourself headaches later.
+Make sure to check over all the settings to make sure they will work in your production environment to save yourself headaches later.
=back
@@ -269,11 +269,11 @@ Once you have done all of the above, your application should be ready to use at
=head2 Updating the Production Server
-After you've made some collection of updates to your Jifty application, you'll then need to install those changes onto your server and prepr your application to use the changes.
+After you've made some collection of updates to your Jifty application, you'll then need to install those changes onto your server and prepare your application to use the changes.
This documentation assumes a "cold" upgrade with the application offline during the duration of the process. A future version of this document might also include instructions for performing a "hot" upgrade without taking the server offline.
-You can do his with the following steps:
+You can do this with the following steps:
=over
@@ -315,7 +315,7 @@ Remember, shutdown all Jifty application processes before continuing, or bad thi
=head4 Shutting Down the Server
-This will involve a two step process. First, you will want to shutodwn your web server. The second is to shutdown the Jifty server. If you are using the built-in Jifty server, you may do this by running:
+This will involve a two step process. First, you will want to shutdown your web server. The second is to shutdown the Jifty server. If you are using the built-in Jifty server, you may do this by running:
bin/jifty server --stop
@@ -382,7 +382,7 @@ Again, you need to look for any configuration updates that need to adjusted. Thi
=head3 Clear Temporary/Cached Files
-This step is important to prevent strange issues from occuring. You remove all files from the following directories:
+This step is important to prevent strange issues from occurring. You remove all files from the following directories:
=over
diff --git a/lib/Jifty/Manual/FAQ.pod b/lib/Jifty/Manual/FAQ.pod
index 35c98c4..6a25180 100644
--- a/lib/Jifty/Manual/FAQ.pod
+++ b/lib/Jifty/Manual/FAQ.pod
@@ -6,7 +6,7 @@ Jifty::Manual::FAQ - Frequently Answered Questions
=head2 I need to make a web based program, is jifty mature enough?
-We built hiveminder.com with it.
+We built L<hiveminder.com> with it.
=head2 What databases does Jifty support?
diff --git a/lib/Jifty/Manual/Glossary.pod b/lib/Jifty/Manual/Glossary.pod
index b9a13de..f5ba87c 100644
--- a/lib/Jifty/Manual/Glossary.pod
+++ b/lib/Jifty/Manual/Glossary.pod
@@ -49,7 +49,7 @@ A B</collection> is a class representing all or a subset of the records stored i
=item constructor
A property of a L</parameter>; the action B<must> have an argument value for
-this paramater in order to be constructed. This is different from
+this parameter in order to be constructed. This is different from
L</mandatory>, in that the user can leave mandatory fields empty. For
instance, the C<id> of a L<Jifty::Action::Record::Update> is a constructor.
See L<Jifty::Action>.
diff --git a/lib/Jifty/Manual/JavaScript.pod b/lib/Jifty/Manual/JavaScript.pod
index 906ea3f..88b73ab 100644
--- a/lib/Jifty/Manual/JavaScript.pod
+++ b/lib/Jifty/Manual/JavaScript.pod
@@ -10,7 +10,7 @@ jQuery, some good refactor is also being done.
This document is written to help JavaScript programmers working for
a Jifty project to understand what's the different before jQuery landed,
-and provide a quick reference for prototypism believers to learn the new wave
+and provide a quick reference for Prototypism believers to learn the new wave
of JavaScript programming in Jifty.
=head1 Migration to jQuery
@@ -20,7 +20,7 @@ that's used to replace Prototype javascript library.
=head2 Selecting elements with jQuery()
-Invokin jQuery function with exactly one string argument will return
+Invoking the jQuery function with exactly one string argument will return
a jQuery object that represents a list of elements. The string is
a CSS selector. For example:
@@ -38,10 +38,10 @@ to C<$(id)>. Selecting elements with C<jQuery()> function always
returns a jQuery object, but not element it self. There are two notice
especially for Jifty world.
-First of all, Jifty develoeprs should always use C<Jifty.$>. Deep in
+First of all, Jifty developers should always use C<Jifty.$>. Deep in
the design of Jifty, there are many kind of elements with C<":">
character in their id. Sadly it is a feature in jQuery to do more
-powerful seleciton with C<":"> character. For example, this selects
+powerful selection with C<":"> character. For example, this selects
current mouse-overed elements:
jQuery(":hover")
@@ -76,7 +76,7 @@ They are defined in jifty.js.
=item Jifty.$( element_id )
-This is a shorthand of document.getElementById function, like the C<$>
+This is a shorthand of C<document.getElementById> function, like the C<$>
function defined in Prototype library. It is also internally used a
lot because many form specific element ID does not get along with
jQuery's selector, which expect the ":" character is used for special
@@ -92,11 +92,11 @@ element object.
=item Jifty.Effect(element, effect_name, option)
-When called, instantly pefrom a js effect on give element. "element" is an
+When called, instantly perform a js effect on the given element. "element" is an
element object.
The last arg "option" is a hash. Currently it's only used for
-specificing callbacks. There are two possible callbacks, before and
+specifying callbacks. There are two possible callbacks, before and
after. You may specify them like this:
Jifty.Effect(element, "Fade", { duration: 2.0 }, {
@@ -129,7 +129,7 @@ Jifty actions.
=item Jifty.Form.Element.getMoniker( element )
Given an element, or an element id, return a string representing a
-moniker of this element. It returs null if the given element is
+moniker of this element. It returns null if the given element is
considered having no moniker at all.
=item Jifty.Form.Element.getAction( element )
@@ -140,7 +140,7 @@ element. The returned value is an Action object.
=item Jifty.Form.Element.getType( element )
Takes an element or an element id, returns the type associated with
-this element. Possible return values are "registraion", "value",
+this element. Possible return values are "registration", "value",
"fallback", or null if the element does not belongs to any of these
types.
@@ -151,8 +151,8 @@ null if the element given does not have a name.
=item Jifty.Form.Element.getValue( element )
-Tkaes an element or an element id, returns the element value. If the
-element is a CHECKBOX or a RADIO button but it's un-checked, returns
+Takes an element or an element id, returns the element value. If the
+element is a CHECKBOX or a RADIO button but it's unchecked, returns
null.
=item Jifty.Form.Element.validate( element )
@@ -279,7 +279,7 @@ The contents of the region or selected element will be completely replaced by th
The server response will be inserted within the region or selected element before the rest of the content.
-=item Bottomer
+=item Bottom
The server response will be inserted within the region or selected element after the rest of the content.
@@ -289,7 +289,7 @@ The content returned by the server will be inserted immediately before and outsi
=item After
-The content returned by the server will be inserted immedately after and outside the given region or element.
+The content returned by the server will be inserted immediately after and outside the given region or element.
=back
@@ -319,7 +319,7 @@ L<http://www.slideshare.net/simon/learning-jquery-in-30-minutes/>
L<http://www.slideshare.net/remy.sharp/prototype-jquery-going-from-one-to-the-other/>
-=item jQuery Officail Documentation
+=item jQuery Official Documentation
L<http://docs.jquery.com/>
diff --git a/lib/Jifty/Manual/JavaScript_zhtw.pod b/lib/Jifty/Manual/JavaScript_zhtw.pod
index 468e07a..89dedde 100644
--- a/lib/Jifty/Manual/JavaScript_zhtw.pod
+++ b/lib/Jifty/Manual/JavaScript_zhtw.pod
@@ -10,7 +10,7 @@ jQuery, some good refactor is also being done.
This document is written to help JavaScript programmers working for
a Jifty project to understand what's the different before jQuery landed,
-and provide a quick reference for prototypism believers to learn the new wave
+and provide a quick reference for Prototypism believers to learn the new wave
of JavaScript programming in Jifty.
=head1 Migration to jQuery
@@ -20,7 +20,7 @@ of JavaScript programming in Jifty.
=head2 Selecting elements with jQuery()
-Invokin jQuery function with exactly one string argument will return
+Invoking the jQuery function with exactly one string argument will return
a jQuery object that represents a list of elements. The string is
a CSS selector. For example:
@@ -38,10 +38,10 @@ to C<$(id)>. Selecting elements with C<jQuery()> function always
returns a jQuery object, but not element it self. There are two notice
especially for Jifty world.
-First of all, Jifty develoeprs should always use C<Jifty.$>. Deep in
+First of all, Jifty developers should always use C<Jifty.$>. Deep in
the design of Jifty, there are many kind of elements with C<":">
character in their id. Sadly it is a feature in jQuery to do more
-powerful seleciton with C<":"> character. For example, this selects
+powerful selection with C<":"> character. For example, this selects
current mouse-overed elements:
jQuery(":hover")
@@ -76,7 +76,7 @@ They are defined in jifty.js.
=item Jifty.$( element_id )
-This is a shorthand of document.getElementById function, like the C<$>
+This is a shorthand of C<document.getElementById> function, like the C<$>
function defined in Prototype library. It is also internally used a
lot because many form specific element ID does not get along with
jQuery's selector, which expect the ":" character is used for special
@@ -92,11 +92,11 @@ element object.
=item Jifty.Effect(element, effect_name, option)
-When called, instantly pefrom a js effect on give element. "element" is an
+When called, instantly perform a js effect on the given element. "element" is an
element object.
The last arg "option" is a hash. Currently it's only used for
-specificing callbacks. There are two possible callbacks, before and
+specifying callbacks. There are two possible callbacks, before and
after. You may specify them like this:
Jifty.Effect(element, "Fade", { duration: 2.0 }, {
@@ -129,7 +129,7 @@ Jifty actions.
=item Jifty.Form.Element.getMoniker( element )
Given an element, or an element id, return a string representing a
-moniker of this element. It returs null if the given element is
+moniker of this element. It returns null if the given element is
considered having no moniker at all.
=item Jifty.Form.Element.getAction( element )
@@ -140,7 +140,7 @@ element. The returned value is an Action object.
=item Jifty.Form.Element.getType( element )
Takes an element or an element id, returns the type associated with
-this element. Possible return values are "registraion", "value",
+this element. Possible return values are "registration", "value",
"fallback", or null if the element does not belongs to any of these
types.
@@ -151,8 +151,8 @@ null if the element given does not have a name.
=item Jifty.Form.Element.getValue( element )
-Tkaes an element or an element id, returns the element value. If the
-element is a CHECKBOX or a RADIO button but it's un-checked, returns
+Takes an element or an element id, returns the element value. If the
+element is a CHECKBOX or a RADIO button but it's unchecked, returns
null.
=item Jifty.Form.Element.validate( element )
@@ -279,7 +279,7 @@ The contents of the region or selected element will be completely replaced by th
The server response will be inserted within the region or selected element before the rest of the content.
-=item Bottomer
+=item Bottom
The server response will be inserted within the region or selected element after the rest of the content.
@@ -289,7 +289,7 @@ The content returned by the server will be inserted immediately before and outsi
=item After
-The content returned by the server will be inserted immedately after and outside the given region or element.
+The content returned by the server will be inserted immediately after and outside the given region or element.
=back
@@ -319,7 +319,7 @@ L<http://www.slideshare.net/simon/learning-jquery-in-30-minutes/>
L<http://www.slideshare.net/remy.sharp/prototype-jquery-going-from-one-to-the-other/>
-=item jQuery Officail Documentation
+=item jQuery Official Documentation
L<http://docs.jquery.com/>
diff --git a/lib/Jifty/Manual/Logging.pod b/lib/Jifty/Manual/Logging.pod
index af40d34..9ecc9c3 100644
--- a/lib/Jifty/Manual/Logging.pod
+++ b/lib/Jifty/Manual/Logging.pod
@@ -12,7 +12,7 @@ Jifty uses the Log4perl module for logging messages, so you can define your own
log4perl config for logging.
You can define different behaviour for different log levels. For example,
-you can send mail to administrator when error occured, or add color to
+you can send mail to administrator when error occurred, or add color to
warning messages that are logged to the terminal.
=head1 Config from config.yml
diff --git a/lib/Jifty/Manual/Models.pod b/lib/Jifty/Manual/Models.pod
index 0af4f65..1cf88a7 100644
--- a/lib/Jifty/Manual/Models.pod
+++ b/lib/Jifty/Manual/Models.pod
@@ -61,7 +61,7 @@ Creating a model has important side effects:
=back
To get all these things done, Jifty allows to describe the schema
-definition in a simply comprehendable but powerful syntax that looks
+definition in a simply comprehensible but powerful syntax that looks
more like written text than a programming language. The schema
definition is made inside the C<MyApp::Model::XXX::Schema> package and
every single column to get created starts with the word C<column>
@@ -121,7 +121,7 @@ Every time you run the jifty utility with C<schema> as an argument,
Jifty will keep track on what it has done for you. To get that done,
the version-number being stored in your application's config file
C<etc/config.yml> under the key named C<framework/Database/Verson> is
-matched agains your schema definition.
+matched against your schema definition.
To force an update of your schema, simple create a new version number
in your config file and modify your schema definition by using exactly
@@ -169,7 +169,7 @@ directly deals with the underlying database.
=item * App::Model::XxxCollection
As the name applies, a collection is a set of typically more than one
-record. Every collection of this class conists of multiple
+record. Every collection of this class consists of multiple
C<App::Model::Xxx> objects that can get retrieved from your data-store
without explicit SQL statements, ordered by any criteria you give,
paged in the fashion you like,
@@ -178,7 +178,7 @@ and iterated sequentially or accessed at random order.
=item * App::Collection
Every collection of your schemata will have this class as its
-base. Usually this class is autocreated by L<Jifty::ClassLoader>. If
+base. Usually this class is automatically created by L<Jifty::ClassLoader>. If
you intend to create new features for all of your collection this will
be your chance to do.
@@ -286,7 +286,7 @@ column is used repeatedly.
Every clause is built up by combining its subclauses (if
any) using the C<entry_aggregator> operator (whose default is I<OR>)
-as a combining operator. Clauses are then I<AND>ed together to yield
+as a combining operator. Clauses are then C<AND>ed together to yield
the final restriction that is finally used to retrieve the records in
question.
diff --git a/lib/Jifty/Manual/ObjectModel.pod b/lib/Jifty/Manual/ObjectModel.pod
index 3bc2b5d..ee63c25 100644
--- a/lib/Jifty/Manual/ObjectModel.pod
+++ b/lib/Jifty/Manual/ObjectModel.pod
@@ -6,7 +6,7 @@ Jifty::Manual::ObjectModel -- An overview of the Jifty object model
Jifty applications are generally built in a similar way. There's no reason
you I<need> to use the model we've built, but we find it a reasonably
-ok way to do things.
+OK way to do things.
This document should serve as a roadmap to the Jifty class library, as
well as an introduction to the way Jifty applications are put together.
@@ -43,10 +43,10 @@ on the fly. It's always possible to I<actually> create these libraries
when you need to customize the default behavior, but we work really
hard to make sure you don't need to.
-Right now, Jifty is autocreating libraries, static web pages and web
+Right now, Jifty is automatically creating libraries, static web pages and web
templates.
-We're not 100% satisfied with how Jifty autocreates web templates and
+We're not 100% satisfied with how Jifty automatically creates web templates and
static pages and are working to redesign that.
The library you I<see> when creating a Jifty app is:
diff --git a/lib/Jifty/Manual/PageRegions.pod b/lib/Jifty/Manual/PageRegions.pod
index 4f83fcc..ae3cb07 100644
--- a/lib/Jifty/Manual/PageRegions.pod
+++ b/lib/Jifty/Manual/PageRegions.pod
@@ -145,7 +145,7 @@ JavaScript usually returns false, the fallback mode is never seen by
the browser.
When a region is output, it is output with a tiny "region wrapper",
-which serves two purposes: to inform the JavaScript of the existance
+which serves two purposes: to inform the JavaScript of the existence
of the page region and its default path and variables, and to create a
unique C<< <div> >> for the fragment to reside in. The browser reads
the JavaScript and creates, on the client-side, a model of the nested
@@ -173,7 +173,7 @@ any messages and errors from actions.
=head3 Hidden information that shows after click on a link
-It's ofetn required to hide some extra information, a list of objects
+It's often required to hide some extra information, a list of objects
or something else under a link. User clicks on the link and the
information you're hiding shows up instead of the link. Regions could
help you to do this task very easy.
@@ -203,7 +203,7 @@ current region, however value of the argument is overriden.
You can add any arguments you want to this component that may be required
to show the additional information, for example an id of some object, but
-you should remeber to use this arguments during links generation.
+you should remember to use this arguments during links generation.
Next thing you should do is to add a region to some page:
diff --git a/lib/Jifty/Manual/RequestHandling.pod b/lib/Jifty/Manual/RequestHandling.pod
index c1ddfa8..81876e3 100644
--- a/lib/Jifty/Manual/RequestHandling.pod
+++ b/lib/Jifty/Manual/RequestHandling.pod
@@ -9,7 +9,7 @@ what happens during the request processing phase.
=head1 THE HANDLER
-As soon as a http request (whatever the method might be, like GET,
+As soon as a HTTP request (whatever the method might be, like GET,
POST, PUT, ...) arrives at Jifty's border, the request is forwarded to
a handler. By default, C<< Jifty->handler >> points to a L<Jifty::Handler>
object that is responsible for handling an incoming request. The
@@ -36,7 +36,7 @@ will become possible.
=item construct a request and response object
Using the L<CGI> object, a L<Jifty::Request> object is constructed and
-its data is populated with the CGI's data. The request can be reached
+its data is populated with the CGI object's data. The request can be reached
later using C<< Jifty->web->request >>. The request holds information
about all actions involved, all page fragments, contains state
variables and arguments (usually GET/POST parameters).
@@ -59,7 +59,7 @@ housed in a C<static> directory, this content is handled.
=item setup the session
-Based on a cookie that is sent with every http response, the current
+Based on a cookie that is sent with every HTTP response, the current
user is assigned a unique session. The session is stored in a
L<Jifty::Web::Session> object and can be accessed using the
C<< Jifty->web->session >> method.
diff --git a/lib/Jifty/Manual/Style.pod b/lib/Jifty/Manual/Style.pod
index ce019c6..ec9dbd4 100644
--- a/lib/Jifty/Manual/Style.pod
+++ b/lib/Jifty/Manual/Style.pod
@@ -43,7 +43,7 @@ run.
=head3 Use Shell::Command
Shell::Command has a number of functions which work like common shell
-file commands such as touch, cp and mv. They are battle tested and
+file commands such as C<touch>, C<cp> and C<mv>. They are battle tested and
cross-platform. Use them instead of coding your own.
For example, instead of this:
diff --git a/lib/Jifty/Manual/Tutorial.pod b/lib/Jifty/Manual/Tutorial.pod
index a0567bc..93c8dc4 100644
--- a/lib/Jifty/Manual/Tutorial.pod
+++ b/lib/Jifty/Manual/Tutorial.pod
@@ -418,7 +418,7 @@ and C<Previous Page> links you now have. Turn off JavaScript or view the page
in C<lynx>, and notice how the AJAX automatically falls-back to page loads for
you. All for free, thanks to Jifty!
-=head3 Hey, where'd that class come from?
+=head3 Hey, where did that class come from?
You may have wondered about C<MyWeblog::Model::PostCollection>, since there's
no file called F<PostCollection.pm>. Jifty uses L<Jifty::ClassLoader> to
diff --git a/lib/Jifty/Manual/jQueryMigrationGuide.pod b/lib/Jifty/Manual/jQueryMigrationGuide.pod
index 19ec12f..d675b59 100644
--- a/lib/Jifty/Manual/jQueryMigrationGuide.pod
+++ b/lib/Jifty/Manual/jQueryMigrationGuide.pod
@@ -46,7 +46,7 @@ localize this alias within a closure:
=head1 Jifty API
-We re-architechted Jifty's javascript libraries to use jQuery. Especially
+We re-architected Jifty's javascript libraries to use jQuery. Especially
the internal functions to process form elements.
The old, Prototype-based way is to extend Form object and the
@@ -65,7 +65,7 @@ use directly.
If you've ever written javascript code for your Jifty applications, and
you'd like to remove the PrototypeJS library, here are some mechanical rules to
-re-write prototypejs-based javascript code with jQuery.
+re-write prototype.js-based javascript code with jQuery.
=head3 Array iteration
diff --git a/lib/Jifty/Model/Metadata.pm b/lib/Jifty/Model/Metadata.pm
index 74c14bc..b0d3182 100644
--- a/lib/Jifty/Model/Metadata.pm
+++ b/lib/Jifty/Model/Metadata.pm
@@ -34,7 +34,7 @@ use base qw( Jifty::Record );
=head2 table
-Schemas are stored in the table C<_jifty_metadata>.
+Each schema is stored in the table C<_jifty_metadata>.
=cut
diff --git a/lib/Jifty/Module/Pluggable.pm b/lib/Jifty/Module/Pluggable.pm
index 9280383..babec33 100644
--- a/lib/Jifty/Module/Pluggable.pm
+++ b/lib/Jifty/Module/Pluggable.pm
@@ -28,7 +28,7 @@ Module::Pluggable used to to use UNIVERSAL::require but I switched
because I was trying to get rid of dependencies.
I farmed the requiring stuff off to it's own _require method in order to
-make it easy to subclass so that people could ovveride how the require
+make it easy to subclass so that people could override how the require
was done.
diff --git a/lib/Jifty/Plugin.pm b/lib/Jifty/Plugin.pm
index 4bf80e3..98777c0 100644
--- a/lib/Jifty/Plugin.pm
+++ b/lib/Jifty/Plugin.pm
@@ -260,7 +260,7 @@ sub bootstrapper {
=head2 upgrade_class
-Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values, and renaming columns). This normally returns the plugin's class name with C<::Upgrade> added to the end. Plugin upgraders can be built in exactly the same was as application upgrade classes.
+Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values, and renaming columns). This normally returns the plugin's class name with C<::Upgrade> added to the end. Plugin upgrade classes can be built in exactly the same was as application upgrade classes.
See L<Jifty::Upgrade>.
diff --git a/lib/Jifty/Plugin/ActorMetadata/Mixin/Model/ActorMetadata.pm b/lib/Jifty/Plugin/ActorMetadata/Mixin/Model/ActorMetadata.pm
index 5126b98..5f174c2 100644
--- a/lib/Jifty/Plugin/ActorMetadata/Mixin/Model/ActorMetadata.pm
+++ b/lib/Jifty/Plugin/ActorMetadata/Mixin/Model/ActorMetadata.pm
@@ -58,7 +58,7 @@ Jifty::DBI::Schema->register_types(
=head1 METHODS
-# XXX: podcoverage should count parent classes. these pods are useless
+# XXX: pod coverage should count parent classes. this pod is useless
=head2 register_triggers
diff --git a/lib/Jifty/Plugin/Authentication/Password/Action/ResetLostPassword.pm b/lib/Jifty/Plugin/Authentication/Password/Action/ResetLostPassword.pm
index ac85656..11428a6 100755
--- a/lib/Jifty/Plugin/Authentication/Password/Action/ResetLostPassword.pm
+++ b/lib/Jifty/Plugin/Authentication/Password/Action/ResetLostPassword.pm
@@ -63,7 +63,7 @@ sub take_action {
my $pass = $self->argument_value('password');
my $pass_c = $self->argument_value('password_confirm');
- # Trying to set a password (ie, submitted the form)
+ # Trying to set a password (i.e., submitted the form)
unless (defined $pass and defined $pass_c and length $pass and $pass eq $pass_c ) {
$self->result->error( _("It looks like you didn't enter the same password into both boxes. Give it another shot?")
);
diff --git a/lib/Jifty/Plugin/Authentication/Password/Dispatcher.pm b/lib/Jifty/Plugin/Authentication/Password/Dispatcher.pm
index 91ab11c..9638f78 100644
--- a/lib/Jifty/Plugin/Authentication/Password/Dispatcher.pm
+++ b/lib/Jifty/Plugin/Authentication/Password/Dispatcher.pm
@@ -14,7 +14,7 @@ All the dispatcher rules jifty needs to support L<Jifty::Authentication::Passwor
=head1 RULES
-=head2 before logout
+=head2 C<before logout>
Logout and return home.
@@ -30,7 +30,7 @@ before 'logout' => run {
# Make sure tangents work
# Before password reminders, login or signup, let's push the user off to the homepage if they're logged in
-=head2 before *
+=head2 C<before *>
Setup the navigation menu for login or logout.
@@ -51,7 +51,7 @@ before '*' => run {
};
-=head2 on qr/^(?:signup|lost_password)$/
+=head2 C<on qr/^(?:signup|lost_password)$/>
Redirect to home if logged.
@@ -64,7 +64,7 @@ before qr'^/(?:signup|lost_password)$' => run {
set 'next' => Jifty->web->request->continuation || Jifty::Continuation->new( request => Jifty::Request->new( path => "/login" ) );
};
-=head2 on login
+=head2 C<on login>
Redirect to home if logged.
@@ -77,7 +77,7 @@ before qr|^/(?:login)$| => run {
set 'next' => Jifty->web->request->continuation || Jifty::Continuation->new( request => Jifty::Request->new( path => "/" ) );
};
-=head2 before reset_lost_password
+=head2 C<before reset_lost_password>
Request a password reset.
@@ -88,7 +88,7 @@ before qr|(?:reset_lost_password)| => run {
};
# Send a password reminder for a lost password
-=head2 before passwordreminder
+=head2 C<before passwordreminder>
Request a new password reminder to be sent by email.
@@ -101,7 +101,7 @@ before 'passwordreminder' => run {
};
-=head2 before signup
+=head2 C<before signup>
Sign up for an account.
@@ -114,7 +114,7 @@ before 'signup' => run {
};
-=head2 before login
+=head2 C<before login>
Login to your account.
diff --git a/lib/Jifty/Plugin/Authentication/Password/Mixin/Model/User.pm b/lib/Jifty/Plugin/Authentication/Password/Mixin/Model/User.pm
index 9332b25..c2ce1a8 100644
--- a/lib/Jifty/Plugin/Authentication/Password/Mixin/Model/User.pm
+++ b/lib/Jifty/Plugin/Authentication/Password/Mixin/Model/User.pm
@@ -170,7 +170,7 @@ sub has_alternative_auth { }
=head2 after_set_password
-Regenerate auth tokens on password change
+Regenerate authentication tokens on password change
=cut
diff --git a/lib/Jifty/Plugin/CSSQuery.pm b/lib/Jifty/Plugin/CSSQuery.pm
index 3bf816f..9b79e33 100644
--- a/lib/Jifty/Plugin/CSSQuery.pm
+++ b/lib/Jifty/Plugin/CSSQuery.pm
@@ -63,11 +63,11 @@ L<http://jifty.org>, L<http://dean.edwards.name/my/cssQuery/>
This plugin is Copyright 2007 Handlino, Inc.
-It is available for modication and distribution under the same terms
+It is available for modification and distribution under the same terms
as Perl itself.
cssQuery is available for use in all personal or commercial projects
-under both MIT and GPL licenses. This means taht you can choose the
+under both MIT and GPL licenses. This means that you can choose the
license that best suits your project and use it accordingly. See
L<http://jifty.com/> for current information on cssQuery copyrights
and licensing.
diff --git a/lib/Jifty/Plugin/ClassLoader.pm b/lib/Jifty/Plugin/ClassLoader.pm
index 9a1aebe..53f55a7 100644
--- a/lib/Jifty/Plugin/ClassLoader.pm
+++ b/lib/Jifty/Plugin/ClassLoader.pm
@@ -5,7 +5,7 @@ package Jifty::Plugin::ClassLoader;
=head1 NAME
-Jifty::Plugin::ClassLoader - Autogenerates application classes
+Jifty::Plugin::ClassLoader - Automatically generates application classes
=head1 DESCRIPTION
@@ -53,7 +53,7 @@ auto-generated:
=item I<Application>
-An empty application base class is created that doen't provide any
+An empty application base class is created that doesn't provide any
methods or inherit from anything.
=item I<Application>::Record
diff --git a/lib/Jifty/Plugin/Compat.pm b/lib/Jifty/Plugin/Compat.pm
index 652ae2c..12e1ba6 100644
--- a/lib/Jifty/Plugin/Compat.pm
+++ b/lib/Jifty/Plugin/Compat.pm
@@ -30,7 +30,7 @@ TODO: this should also rebind STDIN/STDOUT in the per-request hook.
=head2 wrap APP
-Wraps the provided Plack app in the compat layer. You'll never need to call
+Wraps the provided Plack app in the compatibility layer. You'll never need to call
this yourself.
=cut
diff --git a/lib/Jifty/Plugin/Config.pm b/lib/Jifty/Plugin/Config.pm
index d269ebf..8a83156 100644
--- a/lib/Jifty/Plugin/Config.pm
+++ b/lib/Jifty/Plugin/Config.pm
@@ -38,7 +38,7 @@ default is '/', 5 and '/__jifty/config', respectively
after_restart_url is the url where we will redirect to after restart
wait_seconds are the seconds that we wait for before redirecting
config_url is the url where we will update the config
-restart_url is the url where we acturally do the restart, with a wait page
+restart_url is the url where we actually do the restart, with a wait page
setting nav_menu to 0 will stop this plugin from adding anything to your application's navigation menu
diff --git a/lib/Jifty/Plugin/Deflater.pm b/lib/Jifty/Plugin/Deflater.pm
index 79f055b..f5d8f16 100644
--- a/lib/Jifty/Plugin/Deflater.pm
+++ b/lib/Jifty/Plugin/Deflater.pm
@@ -17,7 +17,7 @@ Jifty::Plugin::Deflater - Handles Accept-Encoding and compression
Plugins:
- Deflater: {}
-# You should put defalter at the end of the plugins list
+# You should put deflater at the end of the plugins list
=head1 DESCRIPTION
diff --git a/lib/Jifty/Plugin/ErrorTemplates/View.pm b/lib/Jifty/Plugin/ErrorTemplates/View.pm
index a92cf66..cf2e157 100644
--- a/lib/Jifty/Plugin/ErrorTemplates/View.pm
+++ b/lib/Jifty/Plugin/ErrorTemplates/View.pm
@@ -49,7 +49,7 @@ template '/error/_elements/error_text' => sub {
=head2 wrapper
This exists as a fallback wrapper, in case the error in question is
-caused by the Jifty app's wrapper, for instance.
+caused by the Jifty application's wrapper, for instance.
=cut
diff --git a/lib/Jifty/Plugin/Halo.pm b/lib/Jifty/Plugin/Halo.pm
index c2bb3bf..45ef817 100644
--- a/lib/Jifty/Plugin/Halo.pm
+++ b/lib/Jifty/Plugin/Halo.pm
@@ -237,7 +237,7 @@ sub new_frame {
=head2 push_frame -> frame
Creates and pushes a frame onto the render stack. Mason's halos do not support
-"around"ing a component, so we fake it with an explicit stack.
+I<arounding> a component, so we fake it with an explicit stack.
This also triggers C<halo_pre_template> for plugins adding halo data.
@@ -266,7 +266,7 @@ sub push_frame {
=head2 pop_frame -> frame
Pops a frame off the render stack. Mason's halos do not support
-"around"ing a component, so we fake it with an explicit stack.
+C<arounding> a component, so we fake it with an explicit stack.
This also triggers C<halo_post_template> for plugins adding halo data.
diff --git a/lib/Jifty/Plugin/I18N.pm b/lib/Jifty/Plugin/I18N.pm
index 0320561..cbd1d0d 100644
--- a/lib/Jifty/Plugin/I18N.pm
+++ b/lib/Jifty/Plugin/I18N.pm
@@ -24,7 +24,7 @@ Jifty::Plugin::I18N - Additional i18n facility such as language selector
=head1 DESCRIPTION
-This plugin provides additional i18n facility to jifty's core i18n
+This plugin provides additional i18n facility to Jifty's core i18n
features, such as compiling l10n lexicon for client side javascript,
and a language selector action.
diff --git a/lib/Jifty/Plugin/IEFixes.pm b/lib/Jifty/Plugin/IEFixes.pm
index 6a3b557..1ba267f 100644
--- a/lib/Jifty/Plugin/IEFixes.pm
+++ b/lib/Jifty/Plugin/IEFixes.pm
@@ -23,7 +23,7 @@ Jifty::Plugin::IEFixes - Add javascript files for IE
cdn: 'http://yourcdn.for.static.prefix/'
- In your app, if you want to add more ie-specific js:
+ In your app, if you want to add more IE-specific js:
my ($ief) = Jifty->find_plugin('Jifty::Plugin::IEFixes')
$ief->add_javascript( qw(file.js) );
diff --git a/lib/Jifty/Plugin/LetMe.pm b/lib/Jifty/Plugin/LetMe.pm
index 2eeb43f..299086c 100644
--- a/lib/Jifty/Plugin/LetMe.pm
+++ b/lib/Jifty/Plugin/LetMe.pm
@@ -10,7 +10,7 @@ Jifty::Plugin::LetMe - Plugin for url-based authentication
=head1 DESCRIPTION
-This plugin provides dispatcher rules to support jifty's internal
+This plugin provides dispatcher rules to support Jifty's internal
C<LetMe> url-based authentication.
=cut
diff --git a/lib/Jifty/Plugin/REST.pm b/lib/Jifty/Plugin/REST.pm
index 1bdeaeb..d239c64 100644
--- a/lib/Jifty/Plugin/REST.pm
+++ b/lib/Jifty/Plugin/REST.pm
@@ -12,7 +12,7 @@ Jifty::Plugin::REST - Add REST web services to your app
=head1 DESCRIPTION
-A RESTian web services API for your Jifty app.
+A RESTful web services API for your Jifty app.
=head1 USAGE
@@ -23,7 +23,7 @@ Add the following to your site_config.yml
- REST: {}
See the URL /=/help in your Jifty app for more information about
-how to access the RESTian resources.
+how to access the REST resources.
=head1 MISC
diff --git a/lib/Jifty/Plugin/REST/Dispatcher.pm b/lib/Jifty/Plugin/REST/Dispatcher.pm
index 9cea1cc..ad222b6 100644
--- a/lib/Jifty/Plugin/REST/Dispatcher.pm
+++ b/lib/Jifty/Plugin/REST/Dispatcher.pm
@@ -53,7 +53,7 @@ Jifty::Plugin::REST::Dispatcher - Dispatcher for REST plugin
=head2 show_help
-Shows basic help about resources and formats available via this RESTian interface.
+Shows basic help about resources and formats available via this RESTful interface.
=cut
@@ -282,8 +282,8 @@ sub output_format {
=head2 outs PREFIX DATASTRUCTURE
-TAkes a url path prefix and a datastructure. Depending on what content types the other side of the HTTP connection can accept,
-renders the content as yaml, json, javascript, perl, xml or html.
+Takes a url path prefix and a data structure. Depending on what content types the other side of the HTTP connection can accept,
+renders the content as YAML, JSON, JavaScript, Perl, XML or HTML.
=cut
@@ -367,7 +367,7 @@ sub render_as_html {
=head2 html_dump DATASTRUCTURE
-Recursively render DATASTRUCTURE as some simple html dls and ols.
+Recursively render DATASTRUCTURE as some simple HTML C<dl>s and C<ol>s.
=cut
@@ -557,7 +557,7 @@ sub list_model_columns {
=head2 list_model_items MODELCLASS COLUMNNAME
-Returns a list of items in MODELCLASS sorted by COLUMNNAME, with only COLUMNAME displayed. (This should have some limiting thrown in)
+Returns a list of items in MODELCLASS sorted by COLUMNNAME, with only COLUMNNAME displayed. (This should have some limiting thrown in)
=cut
@@ -939,7 +939,7 @@ Returns the action's result.
TODO, doc the format of the result.
On an invalid action name, throws a C<404>.
-On a disallowed action mame, throws a C<403>.
+On a disallowed action name, throws a C<403>.
On an internal error, throws a C<500>.
=cut
diff --git a/lib/Jifty/Plugin/RequestInspector.pm b/lib/Jifty/Plugin/RequestInspector.pm
index a18dfd1..8ee0153 100644
--- a/lib/Jifty/Plugin/RequestInspector.pm
+++ b/lib/Jifty/Plugin/RequestInspector.pm
@@ -264,7 +264,7 @@ Returns a list of plugin instances that hook into RequestInspector.
=head2 new_request_inspection
-Instantiates a new request inspection, setting up some defalt values.
+Instantiates a new request inspection, setting up some default values.
=head2 should_handle_request CGI
diff --git a/lib/Jifty/Plugin/SQLQueries.pm b/lib/Jifty/Plugin/SQLQueries.pm
index 69c5493..a9dd04a 100644
--- a/lib/Jifty/Plugin/SQLQueries.pm
+++ b/lib/Jifty/Plugin/SQLQueries.pm
@@ -96,7 +96,7 @@ __END__
=head1 NAME
-Jifty::Plugin::SQLQueries - Inspect your app's SQL queries
+Jifty::Plugin::SQLQueries - Inspect your application's SQL queries
=head1 DESCRIPTION
diff --git a/lib/Jifty/Plugin/TestServerWarnings/View.pm b/lib/Jifty/Plugin/TestServerWarnings/View.pm
index c9c1f9e..55814a4 100644
--- a/lib/Jifty/Plugin/TestServerWarnings/View.pm
+++ b/lib/Jifty/Plugin/TestServerWarnings/View.pm
@@ -6,7 +6,7 @@ use Jifty::View::Declare -base;
=head1 NAME
-Jifty::Plugin::TestServerWarnings::View - Test warnings downloader
+Jifty::Plugin::TestServerWarnings::View - Downloads test warnings
=head1 TEMPLATES
diff --git a/lib/Jifty/Plugin/ViewDeclarePage/Page.pm b/lib/Jifty/Plugin/ViewDeclarePage/Page.pm
index dd3b788..6187e62 100644
--- a/lib/Jifty/Plugin/ViewDeclarePage/Page.pm
+++ b/lib/Jifty/Plugin/ViewDeclarePage/Page.pm
@@ -13,7 +13,7 @@ Jifty::View::Declare::Page::NewStyle - new style page wrapper to simplify custom
This library is a replacement for L<Jifty::View::Declare::Page>.
That is in Jifty for a while and can not be replaced with something
-completly different because of backwards compatibility.
+completely different because of backwards compatibility.
When you declare a L<Jifty::View::Declare> template that is a page, for example:
@@ -32,7 +32,7 @@ Page classes implement such layouts.
It's very hard to extended L<Jifty::View::Declare::Page> class as
it's written in such a way that forces you to copy&paste some
internals from the class to make overriden method work and don't
-breake things.
+break things.
I think this implementation is much better thing. To use this class
as a base for all your pages you can just add this plugin to your app
@@ -174,13 +174,13 @@ sub init {
Renders whole page from doctype till closing html tag. Takes
no arguments.
-This method drives rendering of the page. Page is splitted
+This method drives rendering of the page. Page is split
into three major parts: header, body and footer. Each is
implemented as corresponding method with 'render_' prefix.
It worth to note that order of rendering is changed and
header is rendered after the body to allow you define page
-title, rss feeds and other thing in content. Read more
+title, RSS feeds and other things in content. Read more
about this below in L</render_header> and L</instrument_content>.
=cut
@@ -468,7 +468,7 @@ sub render_doctype {
=head3 render_title_inhead
Should output nothing but a title tag what will be placed into the head.
-Title is passed as onyl argument. Arguments are combined.
+Title is passed as only argument. Arguments are combined.
=cut
diff --git a/lib/Jifty/Record.pm b/lib/Jifty/Record.pm
index 9fb6668..ed4f8a6 100644
--- a/lib/Jifty/Record.pm
+++ b/lib/Jifty/Record.pm
@@ -39,7 +39,7 @@ C<create> can be called as either a class method or an object method.
Takes an array of key-value pairs and inserts a new row into the
database representing this object.
-Override's L<Jifty::DBI::Record> in these ways:
+Overrides L<Jifty::DBI::Record> in these ways:
=over 4
@@ -345,7 +345,7 @@ for any allow or denial. See L</The before_access hook>.
=item 3.
Next, the default implementation returns true if the current user is a
-superuser or a boostrap user.
+superuser or a bootstrap user.
=item 4.
@@ -596,7 +596,7 @@ sub _brief_description {'name'}
=head2 null_reference
-By default, L<Jifty::DBI::Record> returns C<undef> on non-existant
+By default, L<Jifty::DBI::Record> returns C<undef> on non-existent
related fields; Jifty prefers to get back an object with an undef id.
=cut
@@ -815,7 +815,7 @@ itself, these use the version found in C<$Jifty::VERSION>.
=item 2.
Any model defined by your application use the database version
-declared in the configuration. In F<etc/config.yml>, this is lcoated
+declared in the configuration. In F<etc/config.yml>, this is located
at:
framework:
diff --git a/lib/Jifty/Request.pm b/lib/Jifty/Request.pm
index f9aabd3..bdeaf9b 100644
--- a/lib/Jifty/Request.pm
+++ b/lib/Jifty/Request.pm
@@ -80,7 +80,7 @@ L<arguments|Jifty::Manual::Glossary/arguments>, and an implementation
class. By default, all actions that are submitted are run; it is
possible to only mark a subset of the submitted actions as "active",
and only the active actions will be run. These will eventually become
-full-fledge L<Jifty::Action> objects.
+full-fledged L<Jifty::Action> objects.
=item state variables
@@ -163,8 +163,8 @@ independent fragments. See L<Jifty::Web::PageRegion>.
=head2 BUILD PARAMHASH
-Creates a new request object. For each key in the I<PARAMHASH>, the
-method of that name is called, with the I<PARAMHASH>'s value as its
+Creates a new request object. For each key in the C<PARAMHASH>, the
+method of that name is called, with the C<PARAMHASH>'s value as its
sole argument.
=cut
@@ -586,7 +586,7 @@ sub parse_form_field_name {
=head2 webform_to_data_structure HASHREF
-Converts the data from a webform's %args to the datastructure that
+Converts the data from a webform's %args to the data structure that
L<Jifty::Request> uses internally.
XXX TODO: ALEX: DOC ME
@@ -753,7 +753,7 @@ sub call_continuation {
Returns from the current continuation, if there is one. If the
request path doesn't match, we call the continuation again, which
should redirect to the right place. If we have to do this, we return
-true, which should be taken as a sign to not process the reqest
+true, which should be taken as a sign to not process the request
further.
=cut
diff --git a/lib/Jifty/Request/Mapper.pm b/lib/Jifty/Request/Mapper.pm
index 6648e7f..c0a3aa7 100644
--- a/lib/Jifty/Request/Mapper.pm
+++ b/lib/Jifty/Request/Mapper.pm
@@ -26,7 +26,7 @@ Extended syntax for generating query parameters. This is used by
L<Jifty::Web::Form::Clickable> for its C<parameters> argument, as well
as for C<results> of continuations.
-Possible syntaxes for each key => value pair in the C<HASH> are:
+Possible formats for each key => value pair in the C<HASH> are:
=over
@@ -110,7 +110,7 @@ sub query_parameters {
Responsible for doing the actual mapping that L</query_parameters>
above sets up. That is, takes magical query parameters and extracts
-the values they were ment to have.
+the values they were meant to have.
=over
diff --git a/lib/Jifty/Schema.pm b/lib/Jifty/Schema.pm
index 8cd15bd..9584db9 100644
--- a/lib/Jifty/Schema.pm
+++ b/lib/Jifty/Schema.pm
@@ -7,7 +7,7 @@ use SQL::ReservedWords;
=head1 NAME
-Jifty::Schema - Jifty schemas
+Jifty::Schema - generates and upgrades your application's schema
=cut
@@ -34,7 +34,7 @@ delete $_SQL_RESERVED{ lc($_) } for (@_SQL_RESERVED_OVERRIDE);
=head2 new
-Returns a new Jifty::Schema. Takes no arguments. Will automatically figure out and initialize the models defined in the app's source.
+Returns a new Jifty::Schema. Takes no arguments. Will automatically figure out and initialize the models defined in the application's source.
=cut
@@ -49,7 +49,7 @@ sub new {
=head2 _init_model_list
-Reads in our application class from the config file and finds all our app's models.
+Reads in our application class from the config file and finds all our application's models.
=cut
@@ -92,7 +92,7 @@ sub serialize_current_schema {
=head2 upgrade_schema
-Looks at the current schemas as defined by the source and the database and updates the database by adding, dropping, and renaming columns.
+Looks at the current schema as defined by the source code and the database and updates the database by adding, dropping, and renaming columns.
=cut
diff --git a/lib/Jifty/Script.pm b/lib/Jifty/Script.pm
index 63a26ab..b2adc74 100644
--- a/lib/Jifty/Script.pm
+++ b/lib/Jifty/Script.pm
@@ -17,8 +17,8 @@ Jifty::Script - Base class for all bin/jifty commands
C<prepare> figures out which command to run. If the user wants
C<--help> give them help.
-In the normal case, let App::CLI figure out the commandline.
-If they have no command on the commandline, but a JIFTY_COMMAND
+In the normal case, let App::CLI figure out the command-line.
+If they have no command on the command-line, but a JIFTY_COMMAND
environment variable, try that. Otherwise, if the GATEWAY_INTERFACE
environment variable is set, assume we are running under CGI with the
C<fastcgi> command. If all fails, shows the help.
diff --git a/lib/Jifty/Script/FastCGI.pm b/lib/Jifty/Script/FastCGI.pm
index 874ace9..518bc6a 100755
--- a/lib/Jifty/Script/FastCGI.pm
+++ b/lib/Jifty/Script/FastCGI.pm
@@ -57,7 +57,7 @@ sub options {
=head1 DESCRIPTION
This command is provided for compatibility. You should probably use
-Plack's fastcgi deployment tools with the C<app.psgi> file come with
+Plack's FastCGI deployment tools with the C<app.psgi> file come with
your jifty app.
@@ -66,7 +66,7 @@ new world-changing application is generating, you'll need something a bit heavie
than the pure-perl Jifty standalone server. C<FastCGI> is what you're looking for.
If you have MaxRequests options under FastCGI in your config.yml, or
-commandline option C<--maxrequests=N> assigned, the fastcgi process
+command-line option C<--maxrequests=N> assigned, the FastCGI process
will exit after serving N requests.
=head1 SERVER CONFIGURATIONS
diff --git a/lib/Jifty/Script/Po.pm b/lib/Jifty/Script/Po.pm
index 47451ac..30fd0fc 100644
--- a/lib/Jifty/Script/Po.pm
+++ b/lib/Jifty/Script/Po.pm
@@ -285,7 +285,7 @@ Jifty::Script::Po - Extract translatable strings from your application
Options:
--language Language to deal with
- --dir Additionl dirs to extract from
+ --dir Additional directories to extract from
--js Generate json files from the current po files
--help brief help message
@@ -303,7 +303,7 @@ name of a message catalog to create.
=item B<--dir>
Specify explicit directories to extract from. Can be used multiple
-times. The default directores will not be extracted if you use this option.
+times. The default directories will not be extracted if you use this option.
=item B<--template_name>
diff --git a/lib/Jifty/Script/Schema.pm b/lib/Jifty/Script/Schema.pm
index 063b3f6..8e6f8aa 100755
--- a/lib/Jifty/Script/Schema.pm
+++ b/lib/Jifty/Script/Schema.pm
@@ -11,7 +11,7 @@ use Jifty::Schema;
=head1 NAME
-Jifty::Script::Schema - Create SQL to update or create your Jifty app's tables
+Jifty::Script::Schema - Create SQL to update or create your Jifty application's tables
=head1 SYNOPSIS
@@ -64,7 +64,7 @@ the same as the application's version.
=item B<--ignore-reserved-words>
-Ignore any SQL reserved words used in table or column deffinitions, if
+Ignore any SQL reserved words used in table or column definitions, if
this option is not used and a reserved word is found it will cause an error.
=item B<--no-bootstrap>
diff --git a/lib/Jifty/Script/Server.pm b/lib/Jifty/Script/Server.pm
index 6e33347..ef89aa7 100755
--- a/lib/Jifty/Script/Server.pm
+++ b/lib/Jifty/Script/Server.pm
@@ -77,7 +77,7 @@ killing the child pid, and let parent pid create a new one
=item --sigready SIGNAL
-Sets the signal number that shouldbe sent to the server's parent
+Sets the signal number that should be sent to the server's parent
process when the server is ready to accept connections.
=item --quiet
diff --git a/lib/Jifty/Subs/Render.pm b/lib/Jifty/Subs/Render.pm
index f20e54d..54d8079 100644
--- a/lib/Jifty/Subs/Render.pm
+++ b/lib/Jifty/Subs/Render.pm
@@ -18,7 +18,7 @@ Jifty::Subs::Render - Helper for subscriptions rendering
=head2 render($id, $callback)
-Render all outstanding messges, and call C<$callback> with render
+Render all outstanding messages, and call C<$callback> with render
mode, region name, and content.
=cut
diff --git a/lib/Jifty/Test/WWW/Mechanize.pm b/lib/Jifty/Test/WWW/Mechanize.pm
index c0ebd5d..23cc76e 100644
--- a/lib/Jifty/Test/WWW/Mechanize.pm
+++ b/lib/Jifty/Test/WWW/Mechanize.pm
@@ -52,7 +52,7 @@ sub new {
=head2 request
-We override mechanize's defualt request method so accept-encoding is
+We override L<WWW::Mechanize>'s default request method so accept-encoding is
not set to gzip by default.
=cut
diff --git a/lib/Jifty/Upgrade.pm b/lib/Jifty/Upgrade.pm
index 311b0f6..f7adf5d 100644
--- a/lib/Jifty/Upgrade.pm
+++ b/lib/Jifty/Upgrade.pm
@@ -3,7 +3,7 @@ use strict;
=head1 NAME
-Jifty::Upgrade - Superclass for schema/data upgrades to Jifty applicaitons
+Jifty::Upgrade - Superclass for schema/data upgrades to Jifty applications
=head1 SYNOPSIS
@@ -32,7 +32,7 @@ Jifty::Upgrade - Superclass for schema/data upgrades to Jifty applicaitons
=head1 DESCRIPTION
-C<Jifty::Upgrade> is an abstract baseclass to use to customize schema
+C<Jifty::Upgrade> is an abstract base class to use to customize schema
and data upgrades that happen.
=cut
diff --git a/lib/Jifty/Upgrade/Internal.pm b/lib/Jifty/Upgrade/Internal.pm
index bcbf8f2..3c384f7 100644
--- a/lib/Jifty/Upgrade/Internal.pm
+++ b/lib/Jifty/Upgrade/Internal.pm
@@ -11,7 +11,7 @@ our $INITIAL_VERSION;
=head1 NAME
-Jifty::Upgrade::Internal - Upgrades to Jifty-specific schemas and data
+Jifty::Upgrade::Internal - Upgrades to Jifty-specific schema and data
=head1 UPGRADES
diff --git a/lib/Jifty/Util.pm b/lib/Jifty/Util.pm
index d2916cc..65358e0 100644
--- a/lib/Jifty/Util.pm
+++ b/lib/Jifty/Util.pm
@@ -298,7 +298,7 @@ sub _require {
=head2 try_to_require Module
-This method works just like L</require>, except that it surpresses the error message
+This method works just like L</require>, except that it suppresses the error message
in cases where the module isn't found.
=cut
@@ -312,7 +312,7 @@ sub try_to_require {
=head2 already_required class
-Helper function to test whether a given class has already been require'd.
+Helper function to test whether a given class has already been loaded.
=cut
diff --git a/lib/Jifty/View/Declare/CRUD.pm b/lib/Jifty/View/Declare/CRUD.pm
index a9e45a5..a35a07d 100644
--- a/lib/Jifty/View/Declare/CRUD.pm
+++ b/lib/Jifty/View/Declare/CRUD.pm
@@ -69,9 +69,9 @@ Basically, you can use this class to do most (and maybe all) of the work you nee
=end pod_coverage
-=head2 mount_view MODELCASS VIEWCLASS /path
+=head2 mount_view MODELCLASS VIEWCLASS /path
-Call this method in your appliation's view class to add the CRUD views you're looking for. Only the first argument is required.
+Call this method in your application's view class to add the CRUD views you're looking for. Only the first argument is required.
Arguments:
@@ -282,7 +282,7 @@ sub edit_columns {
=head2 create_columns ACTION
Returns a list of all of the columns that this REST view should
-displat for create. Defaults to L</edit_columns>.
+display for create. Defaults to L</edit_columns>.
=cut
diff --git a/lib/Jifty/View/Declare/CoreTemplates.pm b/lib/Jifty/View/Declare/CoreTemplates.pm
index dec6de5..b28bc29 100644
--- a/lib/Jifty/View/Declare/CoreTemplates.pm
+++ b/lib/Jifty/View/Declare/CoreTemplates.pm
@@ -33,7 +33,7 @@ This library contains templates that Jifty can't function without:
=for later
-These templates are still in masonland. we're doign something wrong with escaping in them
+These templates are still in Masonland. we're doing something wrong with escaping in them
template '__jifty/subs' => sub {
diff --git a/lib/Jifty/View/Mason/Handler.pm b/lib/Jifty/View/Mason/Handler.pm
index 20e667f..ebb1c0e 100644
--- a/lib/Jifty/View/Mason/Handler.pm
+++ b/lib/Jifty/View/Mason/Handler.pm
@@ -165,7 +165,7 @@ sub escape_uri {
=head2 template_exists COMPONENT
Checks if the C<COMPONENT> exists, or if C<COMPONENT/index.html>
-exists, and returns which one did. If neither did, it seaches for
+exists, and returns which one did. If neither did, it searches for
C<dhandler> components which could match, returning C<COMPONENT> if it
finds one. Finally, if it finds no possible component matches,
returns undef.
@@ -239,7 +239,7 @@ sub request_args {
=head2 create_cache_directories
-Attempts to create our app's mason cache directory.
+Attempts to create our application's mason cache directory.
=cut
diff --git a/lib/Jifty/Web.pm b/lib/Jifty/Web.pm
index 98e9e7b..c9a65bc 100644
--- a/lib/Jifty/Web.pm
+++ b/lib/Jifty/Web.pm
@@ -167,7 +167,7 @@ sub url {
=head3 serial
Returns a unique identifier, guaranteed to be unique within the
-runtime of a particular process (ie, within the lifetime of Jifty.pm).
+runtime of a particular process (i.e., within the lifetime of Jifty.pm).
There's no sort of global uniqueness guarantee, but it should be good
enough for generating things like moniker names.
@@ -1266,7 +1266,7 @@ The L<add_javascript> method will append the files to javascript_libs.
If you need a different order, you'll have to massage javascript_libs
directly.
-Jifty will look for javascript libraries under share/web/static/js/ by
+Jifty will look for javascript libraries under F<share/web/static/js/> by
default as well as any plugin static roots.
=cut
@@ -1312,7 +1312,7 @@ Removes the given files from C<< Jifty->web->javascript_libs >>.
This is intended for plugins or applications that provide another version of
the functionality given in our default JS libraries. For example, the CSSQuery
-plugin will get rid of the cssQuery-jQuery.js back-compat script.
+plugin will get rid of the F<cssQuery-jQuery.js> back-compat script.
=cut
@@ -1327,7 +1327,7 @@ sub remove_javascript {
=head3 add_external_javascript URL1, URL2, ...
-Pushes urls onto C<< Jifty->web->external_javascript_libs >>
+Pushes URLs onto C<< Jifty->web->external_javascript_libs >>
=cut
diff --git a/lib/Jifty/Web/Form.pm b/lib/Jifty/Web/Form.pm
index 5095a56..7d69e4c 100644
--- a/lib/Jifty/Web/Form.pm
+++ b/lib/Jifty/Web/Form.pm
@@ -158,7 +158,7 @@ sub register_action {
=head2 has_action MONIKER
-If this form has an action whose monkier is C<MONIKER>, returns
+If this form has an action whose moniker is C<MONIKER>, returns
it. Otherwise returns undef.
=cut
diff --git a/lib/Jifty/Web/Form/Clickable.pm b/lib/Jifty/Web/Form/Clickable.pm
index 29d2535..3d1fc46 100644
--- a/lib/Jifty/Web/Form/Clickable.pm
+++ b/lib/Jifty/Web/Form/Clickable.pm
@@ -86,7 +86,7 @@ See L<Jifty::Request::Mapper/query_parameters> for details.
=item submit
A list of actions to run when the object is clicked. This may be an
-array refrence or a single element; each element may either be a
+array reference or a single element; each element may either be a
moniker or, a L<Jifty::Action> or a hashref with the keys 'action' and 'arguments'.
An undefined value submits B<all> actions in the form, an empty list
reference (the default) submits none.
@@ -274,7 +274,7 @@ L<Jifty::Request::Mapper> for details.
=head2 submit [VALUE]
Gets or sets the list of actions to run when the object is clicked.
-This may be an array refrence or a single element; each element may
+This may be an array reference or a single element; each element may
either be a moniker or a L<Jifty::Action>. An undefined value submits
B<all> actions in the form, an empty list reference (the default)
submits none.
@@ -287,7 +287,7 @@ otherwise.
=head2 parameter KEY VALUE
-Sets the given HTTP paramter named C<KEY> to the given C<VALUE>.
+Sets the given HTTP parameter named C<KEY> to the given C<VALUE>.
=cut
@@ -644,7 +644,7 @@ sub generate {
=head2 register_action ACTION
-Reisters the action if it isn't registered already, but only on the
+Registers the action if it isn't registered already, but only on the
link. That is, the registration will not be seen by any other buttons
in the form.
diff --git a/lib/Jifty/Web/Form/Element.pm b/lib/Jifty/Web/Form/Element.pm
index a9a313d..64a7810 100644
--- a/lib/Jifty/Web/Form/Element.pm
+++ b/lib/Jifty/Web/Form/Element.pm
@@ -100,7 +100,7 @@ specified will override arguments submitted by form field.
If you explicitly pass C<undef>, then all actions will be submitted.
This can be useful in conjunction with an C<onclick> handler, since
-declaring an C<onclick> handler inentionally turns off action submission.
+declaring an C<onclick> handler intentionally turns off action submission.
=item disable => BOOLEAN
diff --git a/lib/Jifty/Web/Form/Field.pm b/lib/Jifty/Web/Form/Field.pm
index b8462ef..af6b3ba 100644
--- a/lib/Jifty/Web/Form/Field.pm
+++ b/lib/Jifty/Web/Form/Field.pm
@@ -33,7 +33,7 @@ Jifty::Web::Form::Field - Web input of some sort
=head1 DESCRIPTION
Describes a form input in a L<Jifty::Action>.
-C<Jifty::Web::Form::Field>s know what action they are on, and aquire
+C<Jifty::Web::Form::Field>s know what action they are on, and acquire
properties from the L<Jifty::Action> which they are part of. Each key
in the L<Jifty::Action/arguments> hash becomes a
C<Jifty::Web::Form::Field> whose L</name> is that key.
@@ -138,7 +138,7 @@ __PACKAGE__->mk_accessors(@new_fields, map { "_$_" } @semiexposed_fields);
=head2 name [VALUE]
-Gets or sets the name of the field. This is seperate from the name of
+Gets or sets the name of the field. This is separate from the name of
the label (see L</label>) and the form input name (see
L</input_name>), though both default to this name. This name should
match to a key in the L<Jifty::Action/arguments> hash. If this
@@ -152,7 +152,7 @@ Gets or sets the CSS display class applied to the label and widget.
=head2 type [VALUE]
Gets or sets the type of the HTML <input> field -- that is, 'text' or
-'password'. Defauts to 'text'.
+'password'. Defaults to 'text'.
=head2 key_binding VALUE
@@ -209,7 +209,7 @@ Gets or sets the preamble located in front of the field.
=head2 multiple [VALUE]
A boolean indicating that the field is multiple.
-aka. has multiple attribute, which is uselful for select field.
+aka. has multiple attribute, which is useful for select field.
=head2 id
@@ -354,7 +354,7 @@ Gets the current value we should be using for this form field.
If the argument is marked as "sticky" (default) and there is a value for this
field from a previous action submit AND that action did not have a "success"
-response, returns that submit's value. Otherwise, returns the action's argument's
+response, returns that submit field's value. Otherwise, returns the action's argument's
default_value for this field.
=cut
@@ -576,7 +576,7 @@ sub render_widget {
=head2 canonicalize_value
Called when a value is about to be displayed. Can be overridden to, for example,
-display only the yyyy-mm-dd portion of a DateTime.
+display only the C<YYYY-MM-DD> portion of a L<DateTime>.
=cut
@@ -646,7 +646,7 @@ sub render_value {
Renders the div tag and javascript necessary to do autocompletion for
this form field. Deprecated internally in favor of L</autocomplete_javascript>,
-but kept for backwards compatability since there exists external code that uses
+but kept for backwards compatibility since there exists external code that uses
it.
=cut
diff --git a/lib/Jifty/Web/Form/Field/Date.pm b/lib/Jifty/Web/Form/Field/Date.pm
index 4d45afd..40e8eac 100644
--- a/lib/Jifty/Web/Form/Field/Date.pm
+++ b/lib/Jifty/Web/Form/Field/Date.pm
@@ -15,7 +15,7 @@ Jifty::Web::Form::Field::Date - Add date pickers to your forms
Output date fields with the class 'date'. If the current user's user object has
a C<calendar_starts_monday> method, and it returns true, the
-'calendar-starts-monday' class is added as well.
+C<calendar-starts-monday> class is added as well.
=cut
@@ -35,7 +35,7 @@ sub classes {
=head2 canonicalize_value
-If the value is a DateTime, return just the ymd portion of it.
+If the value is a DateTime, return just the C<ymd> portion of it.
=cut
diff --git a/lib/Jifty/Web/Form/Field/Upload.pm b/lib/Jifty/Web/Form/Field/Upload.pm
index b56721f..efff91c 100644
--- a/lib/Jifty/Web/Form/Field/Upload.pm
+++ b/lib/Jifty/Web/Form/Field/Upload.pm
@@ -10,7 +10,7 @@ Jifty::Web::Form::Field::Upload - File upload field
=head1 DESCRIPTION
An input field that renders using C<< <input type="file" /> >>. The
-argument value that the action recieves from this field via
+argument value that the action receives from this field via
L<Jifty::Action/argument_value> will be a filehandle, which can be
read in the usual ways.
diff --git a/lib/Jifty/Web/Form/Field/Uploads.pm b/lib/Jifty/Web/Form/Field/Uploads.pm
index a78243e..86f8e8c 100644
--- a/lib/Jifty/Web/Form/Field/Uploads.pm
+++ b/lib/Jifty/Web/Form/Field/Uploads.pm
@@ -10,7 +10,7 @@ Jifty::Web::Form::Field::Uploads - File uploads field
=head1 DESCRIPTION
An input field that renders using C<< <input type="file" /> >>. The
-argument value that the action recieves from this field via
+argument value that the action receives from this field via
L<Jifty::Action/argument_value> will be a filehandle, which can be
read in the usual ways.
diff --git a/lib/Jifty/Web/Menu.pm b/lib/Jifty/Web/Menu.pm
index f106223..0508b89 100644
--- a/lib/Jifty/Web/Menu.pm
+++ b/lib/Jifty/Web/Menu.pm
@@ -491,7 +491,7 @@ sub render_as_yui_menu {
=head2 render_as_yui_menubar
Render menubar with YUI menu, suitable for an application's menu.
-It can support arbitary levels of submenu.
+It can support arbitrary levels of submenu.
=cut
diff --git a/lib/Jifty/Web/PageRegion.pm b/lib/Jifty/Web/PageRegion.pm
index dd1d8a4..aaa8387 100644
--- a/lib/Jifty/Web/PageRegion.pm
+++ b/lib/Jifty/Web/PageRegion.pm
@@ -65,7 +65,7 @@ Defaults to true.
=item lazy (optional)
Delays the loading of the fragment until client render-time.
-Obviously, does not work with downlevel browsers which don't uspport
+Obviously, does not work with downlevel browsers which don't support
javascript.
=item loading_path (optional)
@@ -413,7 +413,7 @@ sub get_element {
=head2 client_cacheable
-Returns the client cacheable state of the regions path. Returns false if the template has not been marked as client cacheable. Otherwise it returns the string "static" or "action" based uon the cacheable attribute set on the template.
+Returns the client cacheable state of the regions path. Returns false if the template has not been marked as client cacheable. Otherwise it returns the string "static" or "action" based on the cacheable attribute set on the template.
=cut
diff --git a/lib/Jifty/Web/Session.pm b/lib/Jifty/Web/Session.pm
index 3fa583f..59d75c6 100644
--- a/lib/Jifty/Web/Session.pm
+++ b/lib/Jifty/Web/Session.pm
@@ -126,7 +126,7 @@ sub get {
Sets the value C<VALUE> for C<KEY> for the session. C<TYPE>, which
defaults to "key", allows values to be set in other namespaces,
including "metadata" and "continuation". C<VALUE> can be an arbitrary
-perl data structue -- C<Jifty::Web::Session> will serialize it for
+perl data structure -- C<Jifty::Web::Session> will serialize it for
you.
=cut
diff --git a/lib/Jifty/Web/Session/JDBI.pm b/lib/Jifty/Web/Session/JDBI.pm
index d919ef7..ca113fd 100644
--- a/lib/Jifty/Web/Session/JDBI.pm
+++ b/lib/Jifty/Web/Session/JDBI.pm
@@ -151,7 +151,7 @@ sub get {
Sets the value C<VALUE> for C<KEY> for the session. C<TYPE>, which
defaults to "key", allows values to be set in other namespaces,
including "metadata" and "continuation". C<VALUE> can be an arbitrary
-perl data structue -- C<Jifty::Web::Session> will serialize it for
+perl data structure -- C<Jifty::Web::Session> will serialize it for
you.
=cut
diff --git a/share/web/static/js/jifty.js b/share/web/static/js/jifty.js
index 38a532c..b4e5db5 100644
--- a/share/web/static/js/jifty.js
+++ b/share/web/static/js/jifty.js
@@ -1924,10 +1924,10 @@ if( !Object.prototype.hasOwnProperty ) {
*
* Jifty.Effect(element, "Fade", { duration: 2.0 });
*
- * When called, instantly pefrom a js effect on give element.
+ * When called, instantly perform a js effect on give element.
*
* The last arg "option" is a hash. Currently it's only used for
- * specificing callbacks. There are two possible callbacks, before
+ * specifying callbacks. There are two possible callbacks, before
* and after. You may specify them like this:
*
* Jifty.Effect(element, "Fade", { duration: 2.0 }, {
diff --git a/share/web/static/js/jquery-1.4.1.js b/share/web/static/js/jquery-1.4.1.js
index 1097010..2bdad08 100644
--- a/share/web/static/js/jquery-1.4.1.js
+++ b/share/web/static/js/jquery-1.4.1.js
@@ -1294,7 +1294,7 @@ jQuery.fn.extend({
classNames = value.split( rspace );
while ( (className = classNames[ i++ ]) ) {
- // check each className given, space seperated list
+ // check each className given, space separated list
state = isBool ? state : !self.hasClass( className );
self[ state ? "addClass" : "removeClass" ]( className );
}
diff --git a/share/web/templates/__jifty/error/_elements/wrapper b/share/web/templates/__jifty/error/_elements/wrapper
index 1570ab4..8adbb9d 100644
--- a/share/web/templates/__jifty/error/_elements/wrapper
+++ b/share/web/templates/__jifty/error/_elements/wrapper
@@ -25,6 +25,6 @@ Alert: Jifty <% Jifty->web->tangent( label => 'administration mode' , url => '/_
<%doc>
This exists as a fallback wrapper, in case the mason error in question
-is caused by the Jifty app's wrapper, for instance.
+is caused by the Jifty application's wrapper, for instance.
</%doc>
diff --git a/share/web/templates/__jifty/error/error.css b/share/web/templates/__jifty/error/error.css
index e59d88a..2ea4ae8 100644
--- a/share/web/templates/__jifty/error/error.css
+++ b/share/web/templates/__jifty/error/error.css
@@ -7,7 +7,7 @@ Jifty->web->response->content_type("text/css");
</%init>
<%doc>
-This exists as a fallback CSS, in case the Jifty app's CSS is causing
+This exists as fallback CSS, in case the Jifty application's CSS is causing
the error.
</%doc>
diff --git a/t/TestApp-Plugin-SetupWizard/lib/TestApp/Plugin/SetupWizard/Test.pm b/t/TestApp-Plugin-SetupWizard/lib/TestApp/Plugin/SetupWizard/Test.pm
index 27c9ae1..63c5612 100644
--- a/t/TestApp-Plugin-SetupWizard/lib/TestApp/Plugin/SetupWizard/Test.pm
+++ b/t/TestApp-Plugin-SetupWizard/lib/TestApp/Plugin/SetupWizard/Test.pm
@@ -34,7 +34,7 @@ sub site_config_is {
my $name = shift;
my $got = eval { Jifty::YAML::LoadFile('etc/site_config.yml') };
- die $@ if $@ && $@ !~ /Cannot read from/ && $@ !~ /is empty or non-existant/;
+ die $@ if $@ && $@ !~ /Cannot read from/ && $@ !~ /is empty or non-existent/;
Test::More::is_deeply($got, $expected, $name);
}
commit 17b4e79fe1ff7384c411d7fd86c4ce950f7866a6
Author: Shawn M Moore <sartak at bestpractical.com>
Date: Wed Dec 8 18:29:43 2010 -0500
Add test file for POD spelling
It currently has a monkeypatch to skip our German, Japanese, and
Chinese translations. See [rt.cpan.org #63755]
diff --git a/t/99-pod-spelling.t b/t/99-pod-spelling.t
new file mode 100644
index 0000000..b738b46
--- /dev/null
+++ b/t/99-pod-spelling.t
@@ -0,0 +1,397 @@
+#!/usr/bin/env perl -w
+
+use strict;
+use Test::More;
+eval "use Test::Spelling";
+plan skip_all => "Test::Spelling required for testing POD spelling" if $@;
+plan skip_all => "Coverage tests only run for authors" unless (-d 'inc/.author');
+
+add_stopwords(<DATA>);
+
+local $ENV{LC_ALL} = 'C';
+set_spell_cmd('aspell list -l en');
+
+# monkeypatch Test::Spelling to hide translated files [rt.cpan.org #63755] {{{
+my @translations = (
+ qr/_de\.pod$/,
+ qr/_ja\.pod$/,
+ qr/_zhtw\.pod$/,
+);
+
+no warnings 'redefine';
+no warnings 'once';
+my $orig = Test::Spelling->can('pod_file_spelling_ok');
+*Test::Spelling::pod_file_spelling_ok = sub {
+ my $file = shift;
+
+ if (grep { $file =~ $_ } @translations) {
+ return ok("ignoring translated file $file");
+ }
+
+ $orig->($file, @_);
+};
+# }}}
+
+all_pod_files_spelling_ok();
+
+__DATA__
+Jifty
+LLC
+Javascript
+login
+mixin
+mixins
+json
+Jifty's
+subdirectories
+webserver
+yml
+javascript
+mimetype
+po
+podir
+FastCGI
+Glasser
+Vandiver
+PARAMHASH
+api
+autocomplete
+jifty
+paramhash
+plugins
+startup
+init
+pre
+Autocompletion
+Canonicalization
+Canonicalizes
+ajax
+autocompleted
+autocompleter
+autocompleters
+autocompletion
+canoncalizes
+canonicalization
+canonicalized
+canonicalizer
+canonicalizers
+canonicalizes
+checkbox
+checkboxes
+metadata
+unsetting
+validator
+validators
+namespace
+whitelist
+ACTIONNAME
+CAS
+filename
+memcached
+ClassLoader
+ClassLoaders
+classloader
+plugin's
+ARGUMENTNAMES
+argumentnames
+refactored
+uri
+webservice
+webservices
+ApplicationClass
+ApplicationName
+BestPractical
+ConfigVersion
+MailerArgs
+Rebless
+Reblessing
+VendorConfig
+Wifty
+YAML
+wiki
+blogging
+changelog
+CurrentUser
+ACL
+request's
+DateTime
+CURRENTUSER
+username
+DateTime's
+UTC
+datetime
+natively
+HTTPS
+PSGI
+RULESET
+Neo
+SSL
+streamy
+METAEXPRESSION
+metaexpression
+wildcard
+wildcards
+subrules
+subcondition
+pubsub
+SQLite
+UTF
+DevelMode
+iso
+latin
+undecoded
+ClassName
+backend
+LetMe
+checksum
+letme
+LogConfig
+LogLevel
+del
+JDBI
+CGI
+FIELDNAME
+TODO
+env
+referer
+url
+webform's
+SQL
+SomePlugin
+reblessed
+multipart
+multi
+runtime
+LogReload
+Postgres
+STDERR
+Ruslan
+Zakirov
+dhandler
+autohandler
+blog
+combobox
+signup
+AccessControl
+JS
+UUID
+superset
+dev
+namespaces
+timestamp
+Automagic
+CSS
+plack
+subrequest
+tuple
+REQ
+ur-time
+ConfirmEmail
+logout
+ActorMetadata
+bootstrapper
+bootstrappers
+onclick
+inline
+folksonomy
+subdirectory
+weblog
+jquery
+jQuery
+PrototypeJS
+Prototypism
+jQueryMigrationGuide
+jQuery's
+PostgreSQL
+PNG
+IMG
+LDAP
+HTC
+Turnbull
+Lighttpd
+ModelColor
+cssQuery
+GPL
+Handlino
+SVK
+html
+apache
+myapp
+AdminMode
+BaseURL
+CPAN
+ServeStaticFiles
+www
+BLOBs
+checkmark
+comboboxes
+unrendered
+classname
+abortable
+database's
+Nagle's
+Changelogger
+Hiveminder's
+Preloading
+UI
+jGrowl
+JavaScript
+workflow
+preload
+preloadable
+preloading
+preloads
+APIs
+CSSQuery
+recursing
+autocompletions
+appender
+back-compat
+POSTed
+REQUESTACTION
+jsonToObj
+objToJson
+DumpFile
+LoadFile
+lookup
+subclause
+mouse-overed
+refactor
+BNF
+architected
+app's
+RDBMS
+DBI
+ORM
+keybindings
+RPC
+arg
+js
+Versioning
+datastore
+roadmap
+webforms
+unadventureously
+PageRegions
+chunked
+overriden
+onclick's
+AJAXified
+Online
+RSS
+online
+stylesheets
+MyWeblog
+Weblogs
+downlevel
+Scriptaculous
+stacktrace
+RESTful
+Plack's
+RequestID
+RequestInspector
+suckish
+localizable
+MaxRequests
+maxrequests
+hashrefs
+param
+ConfigFileVersion
+arounding
+TABLEs
+CheckSchema
+BASECLASS
+UPGRADECLASS
+HOSTNAME
+middleware
+minifier
+psgi
+deflater
+versioned
+devel
+jsmin
+appenders
+ajaxautocompletes
+ajaxcanonicalization
+ajaxvalidation
+submenu
+toplevel
+AdminUI
+OnlineDocs
+dropdown
+dropdowns
+beforehash
+submenus
+ajaxy
+menubar
+SetupWizard
+lighttpd
+refactoring
+SkeletonApp
+SinglePage
+COLUMNNAME
+SQLQueries
+redispatching
+CreateModel
+MODELCLASS
+DeleteModel
+tooltip
+internationalizations
+lang
+tooltips
+keybinding
+lightbox
+onblur
+onchange
+ondblclick
+onfocus
+onkeydown
+onkeypress
+onkeyup
+onload
+onmousedown
+onmousemove
+onmouseout
+onmouseover
+onmouseup
+onreset
+onselect
+onsubmit
+onunload
+popout
+beforeclick
+javascript's
+STDOUT
+dhandlers
+SCALARREF
+webpage
+subcomponent
+subcomponents
+doctype
+prepends
+TEMPLATENAME
+VIEWCLASS
+canonicalizeaction
+clkao
+IP
+XHTML
+DATASTRUCTURE
+UpdateModel
+YUI
+CONTID
+Masonland
+rc
+subclassable
+cacheable
+beforeshow
+paramhash's
+Refactorings
+Fh
+upload's
+dir
+dbiprof
+sigready
+ok
+validationaction
+pushfrag
+
-----------------------------------------------------------------------
More information about the Jifty-commit
mailing list