openstack/deb-python-pecan
Code Issues Proposed changes

Fix typos in documents and comments

Browse Source 
Fix typos detected by toolkit misspellings.

* pip install misspellings
* git ls-files | grep -v locale | misspellings -f -

Change-Id: I3d7c06bcc3b5d0cdf82b8da98a7fba15e935cab6
This commit is contained in:
Chang Bo Guo
2013-12-10 05:22:48 -08:00
parent 4d372ecc87
commit 5c9c54bc09
5 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/deployment.rst
View File

@@ -18,7 +18,7 @@ probably vary.
Installing Pecan
----------------
A few popular options are avaliable for installing Pecan in production
A few popular options are available for installing Pecan in production
environments:
* Using `setuptools/distribute
@@ -249,7 +249,7 @@ application should be served. This is how the script (named ``run.py``) looks::
}
return cherrypy.tree.mount(Root(), '/', config=configuration)
# Assuming your app has media on diferent paths, like 'css', and 'images'
# Assuming your app has media on different paths, like 'css', and 'images'
application = wsgiserver.WSGIPathInfoDispatcher({
'/': simpleapp_wsgi_app,
'/css': make_static_config('css'),

2
docs/source/quick_start.rst
View File

@@ -230,7 +230,7 @@ now, let's examine the sample project, controller by controller::
def index(self):
return dict()
The :func:`index` method is marked as *publically available* via the :func:`@expose`
The :func:`index` method is marked as *publicly available* via the :func:`@expose`
decorator (which in turn uses the ``index.html`` template) at the root of the
application (http://127.0.0.1:8080/), so any HTTP ``GET`` that hits the root of
your application (``/``) will be routed to this method.

2
pecan/extensions.py
View File

@@ -31,7 +31,7 @@ class PecanExtensionImporter(object):
This is mostly for convenience and consistency. In this way, Pecan can
maintain an ecosystem of extensions that share a common namespace,
``pecan.ext``, while still maintaining backwards compatability for simple
``pecan.ext``, while still maintaining backwards compatibility for simple
package names (e.g., ``pecancelery``).
"""

4
pecan/hooks.py
View File

@@ -242,14 +242,14 @@ class RequestViewerHook(PecanHook):
**blacklist**
This key holds items that will be blacklisted based on ``url``. If
there is a need to ommit urls that start with `/javascript`, then this
there is a need to omit urls that start with `/javascript`, then this
key would look like::
'blacklist': ['/javascript']
As many blacklisting items as needed can be contained in the list. The hook
will verify that the url is not starting with items in this list to display
results, otherwise it will get ommited.
results, otherwise it will get omitted.
.. note::
This key should always use a ``list`` of items to use.

6
pecan/middleware/resources/shCore.js vendored
View File

@@ -927,7 +927,7 @@ function fixInputString(str)
};
/**
* Removes all white space at the begining and end of a string.
* Removes all white space at the beginning and end of a string.
*
* @param {String} str String to trim.
* @return {String} Returns string without leading and following white space characters.
@@ -968,7 +968,7 @@ function unindent(str)
min = Math.min(matches[0].length, min);
}
// trim minimum common number of white space from the begining of every line
// trim minimum common number of white space from the beginning of every line
if (min > 0)
for (var i = 0; i < lines.length; i++)
lines[i] = lines[i].substr(min);
@@ -1666,7 +1666,7 @@ sh.Highlighter.prototype = {
* Initializes the highlighter/brush.
*
* Constructor isn't used for initialization so that nothing executes during necessary
* `new SyntaxHighlighter.Highlighter()` call when setting up brush inheritence.
* `new SyntaxHighlighter.Highlighter()` call when setting up brush inheritance.
*
* @param {Hash} params Highlighter parameters.
*/