Author: sebawagner
Date: Sat Jan 21 13:47:18 2012
New Revision: 1234324

URL: http://svn.apache.org/viewvc?rev=1234324&view=rev
Log:
Fix typo in new custom room type documentation

Modified:
    incubator/openmeetings/trunk/singlewebapp/docs/CustomRoomTypeHowTo.html
    incubator/openmeetings/trunk/singlewebapp/xdocs/CustomRoomTypeHowTo.xml

Modified: 
incubator/openmeetings/trunk/singlewebapp/docs/CustomRoomTypeHowTo.html
URL: 
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/docs/CustomRoomTypeHowTo.html?rev=1234324&r1=1234323&r2=1234324&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/docs/CustomRoomTypeHowTo.html 
(original)
+++ incubator/openmeetings/trunk/singlewebapp/docs/CustomRoomTypeHowTo.html Sat 
Jan 21 13:47:18 2012
@@ -789,14 +789,14 @@ limitations under the License.
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>Letes start with creating your custom 
room type class.
+                                    <p>Lets start by creating your custom room 
type class.
                                <br />
-                                       Therefore you could for example start 
by duplicating an existing one, from <br />
+                                       You could for example duplicate an 
existing room class, from <br />
                                        
<tt>src/modules/conference/flexibleConferenceRoom</tt> folder, for example the 
-                       flexibleConferenceRoom.lzx, generate a duplicate, 
change the name, for example to 
-                       myCustomConferenceRoom.lzx, and edit the class name 
inside the file name="flexibleConferenceRoom" to
+                       flexibleConferenceRoom.lzx: Generate a duplicate, 
change the name, for example to 
+                       myCustomConferenceRoom.lzx and edit the class name 
inside the file name="flexibleConferenceRoom" to
                        name="myCustomConferenceRoom". Also don't miss to add 
an entry to library.lzx so that the compiler 
-                       finds your new class.
+                       will find your new class.
                        </p>
                             </blockquote>
         </p>

Modified: 
incubator/openmeetings/trunk/singlewebapp/xdocs/CustomRoomTypeHowTo.xml
URL: 
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/CustomRoomTypeHowTo.xml?rev=1234324&r1=1234323&r2=1234324&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/CustomRoomTypeHowTo.xml 
(original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/CustomRoomTypeHowTo.xml Sat 
Jan 21 13:47:18 2012
@@ -30,14 +30,14 @@
                
                <section name="Create your own room type class (User 
Interface)">
                        
-                       <p>Letes start with creating your custom room type 
class.
+                       <p>Lets start by creating your custom room type class.
                                <br/>
-                                       Therefore you could for example start 
by duplicating an existing one, from <br/>
+                                       You could for example duplicate an 
existing room class, from <br/>
                                        
<tt>src/modules/conference/flexibleConferenceRoom</tt> folder, for example the 
-                       flexibleConferenceRoom.lzx, generate a duplicate, 
change the name, for example to 
-                       myCustomConferenceRoom.lzx, and edit the class name 
inside the file name="flexibleConferenceRoom" to
+                       flexibleConferenceRoom.lzx: Generate a duplicate, 
change the name, for example to 
+                       myCustomConferenceRoom.lzx and edit the class name 
inside the file name="flexibleConferenceRoom" to
                        name="myCustomConferenceRoom". Also don't miss to add 
an entry to library.lzx so that the compiler 
-                       finds your new class.
+                       will find your new class.
                        </p>
                        
                </section>


Reply via email to