# New Ticket Created by Saleem A. Ansari # Please include the string: [perl #61638] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61638 >
Fixed typos in docs. book/ch01_overview.pod | 10 +++++----- book/ch03_pir_basics.pod | 2 +- imcc/imcfaq.pod | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-)
Index: docs/book/ch01_overview.pod =================================================================== --- docs/book/ch01_overview.pod (revision 34295) +++ docs/book/ch01_overview.pod (working copy) @@ -25,7 +25,7 @@ working hard on a spec for "Python 3000". The Perl 6 project started moving in two different directions at once: the underlying interpreter architecture and the language grammar and semantics. As people -realized that the two projects could become completely indepent, it +realized that the two projects could become completely independent, it was decided to create a proper language-agnostic virtual machine to support the high-level efforts. The virtual machine was later dubbed "Parrot" in a fitting turn of life imitating art. @@ -105,7 +105,7 @@ members of the Project Team, or may be held jointly. The Architect also works with the Release Managers to develop and maintain the release schedule. Allison RandalX<Randal, Allison> currently leads the Parrot -project aschief architect. +project as chief architect. =item Release Managers @@ -166,7 +166,7 @@ Contributors who submit numerous, high-quality patches may be considered to become a Committer. Committers have commit access to the full Parrot repository, but generally work only on one or more -subprojects; Committer categories are described below. Contributors may +subprojects; Committer categories are described below. Contributors may be considered for commit access either by being nominated by another Committer, or by requesting it. @@ -194,7 +194,7 @@ =item Build Manager Build Managers maintain and extend configuration and build subsystems. -They reviews smoke reports and attempt to extend platform support. +They review smoke reports and attempt to extend platform support. =item Lead Tester @@ -225,7 +225,7 @@ Parrot's cage, the development working environment, has a tendency to get messy and disorganized over time. It's the responsibility of the -aptly-named Cage Cleaners to ensure coding standards are followed, that +aptly-named Cage Cleaners to ensure that coding standards are followed, that documentation is complete and accurate, that all tests are functioning properly, and that there are plenty of coding examples for new users to learn from. A class of tickets in the RT tracking system has been created Index: docs/book/ch03_pir_basics.pod =================================================================== --- docs/book/ch03_pir_basics.pod (revision 34295) +++ docs/book/ch03_pir_basics.pod (working copy) @@ -106,7 +106,7 @@ register data is held. A memory allocator unit translates register names in the form "$S0" into an actual fixed memory location. This allocator can also help to optimize register usage so that existing registers are -reused instead of allocating new ones in memory. The sort version is that +reused instead of allocating new ones in memory. The short version is that the programmer should never have to worry about register allocation, and should feel free to use as many as she wants. As with any system, it's a good idea to be mindful of the things that might impact performance Index: docs/imcc/imcfaq.pod =================================================================== --- docs/imcc/imcfaq.pod (revision 34295) +++ docs/imcc/imcfaq.pod (working copy) @@ -146,9 +146,9 @@ For more examples see the PIR tutorial in F<examples/tutorial>. -=head2 How do I compile and run an PIR module? +=head2 How do I compile and run a PIR module? -Parrot uses the filename extension to detect whether the file is an PIR file +Parrot uses the filename extension to detect whether the file is a PIR file (.pir), a Parrot Assembly file (.pasm) or a pre-compiled bytecode file (.pbc).
