Commits

Virgil Dupras committed b0dbf85

Fixed a few typos in doc.

  • Participants
  • Parent commits d1529da

Comments (0)

Files changed (3)

 
     $ python build.py
 
-You'll normally end up with a usage .app file in the ``build/release`` subfolder.
+You'll normally end up with a .app file in the ``build/release`` subfolder.
 
 Ok, actually there's only one example, and I can't think of another use for pluginbuilder than to 
 wrap a PyObjC-enabled app, but let's pretend there's more than one example...
 Although the argument used by command line and direct invocation are the same, they're formatted
 differently. The boolean flags are turned on with ``--argname`` if their default value is off, and
 turned off with ``--no-argname`` if their default value is on. Arguments receiving a value (anything
-not boolean) are give in the ``--argname value`` format. If the argument receives a list, it must be
-given in the ``--argname item1 item2`` format. If the argument value contains a space character,
+not boolean) are given in the ``--argname value`` format. If the argument receives a list, it must 
+be given in the ``--argname item1 item2`` format. If the argument value contains a space character,
 then the value should be "quoted" (Example: ``--argname item1 "item 2"``. Arguments having
 underscores ("_") in their name have them replaced by dashes ("-") for command line invocation.
 

doc/whyplugin.rst

 ============================
 
 Why embedding a Python plugin into an Objective-C application rather than the other way around
-(driving the Objective-C runtime tom Python)? I wrote an `article about that <http://www.hardcoded.net/articles/embedded-pyobjc.htm>`__ a while ago. Here's an excerpt:
+(driving the Objective-C runtime from Python)? I wrote an `article about that <http://www.hardcoded.net/articles/embedded-pyobjc.htm>`__ a while ago. Here's an excerpt:
 
 **Speed.** In a GUI application, there's usually many, *many* calls being made all the time by the different elements of the GUI. For example, ``NSTableView``'s datasource and delegate methods are called tons of times at each redraw. Each calls having to pass through the PyObjC bridge is inherently slower than a native call. While machines are usually fast enough for this not to be noticeable most of the time, there might be situations where it's not the case, scrolling a large list for example.