Updated HTML docs.

docs/1.0/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Building-Quickstart.html

@@ -129,13 +129,9 @@ is the only room in the game at this point. Let’s explore the commands a littl
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span> create/drop box
 </pre></div>
 </div>
-<p>A <em>/switch</em> is a special, optional flag to the command to make it behave differently. It is always
-put directly after the command name, and begins with a forward slash (<code class="docutils literal notranslate"><span class="pre">/</span></code>). The <em>arguments</em> are one
-or more inputs to the commands. It’s common to use an equal sign (<code class="docutils literal notranslate"><span class="pre">=</span></code>) when assigning something to
-an object.</p>
+<p>A <em>/switch</em> is a special, optional flag to the command to make it behave differently. It is always put directly after the command name, and begins with a forward slash (<code class="docutils literal notranslate"><span class="pre">/</span></code>). The <em>arguments</em> are one or more inputs to the commands. It’s common to use an equal sign (<code class="docutils literal notranslate"><span class="pre">=</span></code>) when assigning something to an object.</p>
 <blockquote>
-<div><p>Are you used to commands starting with &#64;, like &#64;create? That will work too. Evennia simply ignores
-the preceeding &#64;.</p>
+<div><p>Are you used to commands starting with &#64;, like &#64;create? That will work too. Evennia simply ignores the preceeding &#64;.</p>
 </div></blockquote>
 <section id="getting-help">
 <h2><span class="section-number">1.1. </span>Getting help<a class="headerlink" href="#getting-help" title="Permalink to this headline">¶</a></h2>
@@ -155,8 +151,7 @@ the preceeding &#64;.</p>
 </pre></div>
 </div>
 <p>This will show you the description of the current location. <code class="docutils literal notranslate"><span class="pre">l</span></code> is an alias.</p>
-<p>When targeting objects in commands, you have two special labels you can use, <code class="docutils literal notranslate"><span class="pre">here</span></code> for the current
-room or <code class="docutils literal notranslate"><span class="pre">me</span></code>/<code class="docutils literal notranslate"><span class="pre">self</span></code> to point back to yourself. So</p>
+<p>When targeting objects in commands, you have two special labels you can use, <code class="docutils literal notranslate"><span class="pre">here</span></code> for the current room or <code class="docutils literal notranslate"><span class="pre">me</span></code>/<code class="docutils literal notranslate"><span class="pre">self</span></code> to point back to yourself. So</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>look me
 </pre></div>
 </div>
@@ -164,18 +159,12 @@ room or <code class="docutils literal notranslate"><span class="pre">me</span></
 </section>
 <section id="stepping-down-from-godhood">
 <h2><span class="section-number">1.3. </span>Stepping Down From Godhood<a class="headerlink" href="#stepping-down-from-godhood" title="Permalink to this headline">¶</a></h2>
-<p>If you just installed Evennia, your very first player account is called user #1, also known as the
-<em>superuser</em> or <em>god user</em>. This user is very powerful, so powerful that it will override many game
-restrictions (such as locks). This can be useful, but it also hides some functionality that you might
-want to test.</p>
+<p>If you just installed Evennia, your very first player account is called user #1, also known as the <em>superuser</em> or <em>god user</em>. This user is very powerful, so powerful that it will override many game restrictions (such as locks). This can be useful, but it also hides some functionality that you might want to test.</p>
 <p>To temporarily step down from your superuser position, you can use the <code class="docutils literal notranslate"><span class="pre">quell</span></code> command in-game:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>quell
 </pre></div>
 </div>
-<p>This will make you start using the permission of your current character’s level instead of your
-superuser level. If you didn’t change any settings, your game Character should have an <em>Developer</em>
-level permission - high as can be without bypassing locks like the superuser does. This will work
-fine for the examples on this page. Use</p>
+<p>This will make you start using the permission of your current character’s level instead of your superuser level. If you didn’t change any settings, your game Character should have an <em>Developer</em> level permission - high as can be without bypassing locks like the superuser does. This will work fine for the examples on this page. Use</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>unquell
 </pre></div>
 </div>
@@ -183,29 +172,20 @@ fine for the examples on this page. Use</p>
 </section>
 <section id="creating-an-object">
 <h2><span class="section-number">1.4. </span>Creating an Object<a class="headerlink" href="#creating-an-object" title="Permalink to this headline">¶</a></h2>
-<p>Basic objects can be anything – swords, flowers, and non-player characters. They are created using
-the <code class="docutils literal notranslate"><span class="pre">create</span></code> command:</p>
+<p>Basic objects can be anything – swords, flowers, and non-player characters. They are created using the <code class="docutils literal notranslate"><span class="pre">create</span></code> command:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>create box
 </pre></div>
 </div>
-<p>This created a new ‘box’ (of the default object type) in your inventory. Use the command <code class="docutils literal notranslate"><span class="pre">inventory</span></code>
-(or <code class="docutils literal notranslate"><span class="pre">i</span></code>) to see it. Now, ‘box’ is a rather short name, let’s rename it and tack on a few aliases.</p>
+<p>This created a new ‘box’ (of the default object type) in your inventory. Use the command <code class="docutils literal notranslate"><span class="pre">inventory</span></code> (or <code class="docutils literal notranslate"><span class="pre">i</span></code>) to see it. Now, ‘box’ is a rather short name, let’s rename it and tack on a few aliases.</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>name box = very large box;box;very;crate
 </pre></div>
 </div>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
 <p>MUD clients and semi-colon:
-Some traditional MUD clients use the semi-colon <code class="docutils literal notranslate"><span class="pre">;</span></code> to separate client inputs. If so,
-the above line will give an error. You need to change your client to use another command-separator
-or to put it in ‘verbatim’ mode. If you still have trouble, use the Evennia web client instead.</p>
+Some traditional MUD clients use the semi-colon <code class="docutils literal notranslate"><span class="pre">;</span></code> to separate client inputs. If so, the above line will give an error. You need to change your client to use another command-separator or to put it in ‘verbatim’ mode. If you still have trouble, use the Evennia web client instead.</p>
 </div>
-<p>We now renamed the box to <em>very large box</em> (and this is what we will see when looking at it), but we
-will also recognize it by any of the other names we give - like <em>crate</em> or simply <em>box</em> as before.
-We could have given these aliases directly after the name in the <code class="docutils literal notranslate"><span class="pre">create</span></code> command. This is true for
-all creation commands - you can always tag on a list of <code class="docutils literal notranslate"><span class="pre">;</span></code>-separated aliases to the name of your
-new object. If you had wanted to not change the name itself, but to only add aliases, you could have
-used the <code class="docutils literal notranslate"><span class="pre">alias</span></code> command.</p>
+<p>We now renamed the box to <em>very large box</em> (and this is what we will see when looking at it), but we will also recognize it by any of the other names we give - like <em>crate</em> or simply <em>box</em> as before. We could have given these aliases directly after the name in the <code class="docutils literal notranslate"><span class="pre">create</span></code> command. This is true for all creation commands - you can always tag on a list of <code class="docutils literal notranslate"><span class="pre">;</span></code>-separated aliases to the name of your new object. If you had wanted to not change the name itself, but to only add aliases, you could have used the <code class="docutils literal notranslate"><span class="pre">alias</span></code> command.</p>
 <p>We are currently carrying the box. Let’s drop it (there is also a shortcut to create and drop in
 one go by using the <code class="docutils literal notranslate"><span class="pre">/drop</span></code> switch, for example <code class="docutils literal notranslate"><span class="pre">create/drop</span> <span class="pre">box</span></code>).</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>drop box
@@ -226,88 +206,61 @@ You see nothing special.
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>desc box = This is a large and very heavy box.
 </pre></div>
 </div>
-<p>If you try the <code class="docutils literal notranslate"><span class="pre">get</span></code> command, we will pick up the box. So far so good, but if we really want this to
-be a large and heavy box, people should <em>not</em> be able to run off with it that easily. To prevent
-this we need to lock it down. This is done by assigning a <em>Lock</em>  to it. Make sure the box was
-dropped in the room, then try this:</p>
+<p>If you try the <code class="docutils literal notranslate"><span class="pre">get</span></code> command, we will pick up the box. So far so good, but if we really want this to be a large and heavy box, people should <em>not</em> be able to run off with it that easily. To prevent this we need to lock it down. This is done by assigning a <em>Lock</em>  to it. Make sure the box was dropped in the room, then try this:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>lock box = get:false()
 </pre></div>
 </div>
-<p>Locks represent a rather <a class="reference internal" href="../../../Components/Locks.html"><span class="doc std std-doc">big topic</span></a>, but for now that will do what we want. This will lock
-the box so noone can lift it. The exception is superusers, they override all locks and will pick it
+<p>Locks represent a rather <a class="reference internal" href="../../../Components/Locks.html"><span class="doc std std-doc">big topic</span></a>, but for now that will do what we want. This will lock the box so noone can lift it. The exception is superusers, they override all locks and will pick it
 up anyway. Make sure you are quelling your superuser powers and try to get the box now:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>&gt; get box
 You can&#39;t get that.
 </pre></div>
 </div>
-<p>Think this default error message looks dull? The <code class="docutils literal notranslate"><span class="pre">get</span></code> command looks for an <a class="reference internal" href="../../../Components/Attributes.html"><span class="doc std std-doc">Attribute</span></a>
-named <code class="docutils literal notranslate"><span class="pre">get_err_msg</span></code> for returning a nicer error messageod (this can be seen from the default <code class="docutils literal notranslate"><span class="pre">get</span></code> command code). You set attributes using the <code class="docutils literal notranslate"><span class="pre">set</span></code> command:</p>
+<p>Think this default error message looks dull? The <code class="docutils literal notranslate"><span class="pre">get</span></code> command looks for an <a class="reference internal" href="../../../Components/Attributes.html"><span class="doc std std-doc">Attribute</span></a> named <code class="docutils literal notranslate"><span class="pre">get_err_msg</span></code> for returning a nicer error messageod (this can be seen from the default <code class="docutils literal notranslate"><span class="pre">get</span></code> command code). You set attributes using the <code class="docutils literal notranslate"><span class="pre">set</span></code> command:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>set box/get_err_msg = It&#39;s way too heavy for you to lift.
 </pre></div>
 </div>
-<p>Try to get it now and you should see a nicer error message echoed back to you. To see what this
-message string is in the future, you can use ‘examine.’</p>
+<p>Try to get it now and you should see a nicer error message echoed back to you. To see what this message string is in the future, you can use ‘examine.’</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>examine box/get_err_msg
 </pre></div>
 </div>
-<p>Examine will return the value of attributes, including color codes. <code class="docutils literal notranslate"><span class="pre">examine</span> <span class="pre">here/desc</span></code> would return
-the raw description of your current room (including color codes), so that you can copy-and-paste to
-set its description to something else.</p>
-<p>You create new Commands (or modify existing ones) in Python outside the game. We will get to that
-later, in the <a class="reference internal" href="Beginner-Tutorial-Adding-Commands.html"><span class="doc std std-doc">Commands tutorial</span></a>.</p>
+<p>Examine will return the value of attributes, including color codes. <code class="docutils literal notranslate"><span class="pre">examine</span> <span class="pre">here/desc</span></code> would return the raw description of your current room (including color codes), so that you can copy-and-paste to set its description to something else.</p>
+<p>You create new Commands (or modify existing ones) in Python outside the game. We will get to that later, in the <a class="reference internal" href="Beginner-Tutorial-Adding-Commands.html"><span class="doc std std-doc">Commands tutorial</span></a>.</p>
 </section>
 <section id="get-a-personality">
 <h2><span class="section-number">1.5. </span>Get a Personality<a class="headerlink" href="#get-a-personality" title="Permalink to this headline">¶</a></h2>
-<p><a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a> are powerful out-of-character objects useful for many “under the hood” things.
-One of their optional abilities is to do things on a timer. To try out a first script, let’s put one
-on ourselves. There is an example script in <code class="docutils literal notranslate"><span class="pre">evennia/contrib/tutorials/bodyfunctions/bodyfunctions.py</span></code>
-that is called <code class="docutils literal notranslate"><span class="pre">BodyFunctions</span></code>. To add this to us we will use the <code class="docutils literal notranslate"><span class="pre">script</span></code> command:</p>
+<p><a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a> are powerful out-of-character objects useful for many “under the hood” things. One of their optional abilities is to do things on a timer. To try out a first script, let’s put one on ourselves. There is an example script in <code class="docutils literal notranslate"><span class="pre">evennia/contrib/tutorials/bodyfunctions/bodyfunctions.py</span></code> that is called <code class="docutils literal notranslate"><span class="pre">BodyFunctions</span></code>. To add this to us we will use the <code class="docutils literal notranslate"><span class="pre">script</span></code> command:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>script self = tutorials.bodyfunctions.BodyFunctions
 </pre></div>
 </div>
-<p>This string will tell Evennia to dig up the Python code at the place we indicate. It already knows
-to look in the <code class="docutils literal notranslate"><span class="pre">contrib/</span></code> folder, so we don’t have to give the full path.</p>
+<p>This string will tell Evennia to dig up the Python code at the place we indicate. It already knows to look in the <code class="docutils literal notranslate"><span class="pre">contrib/</span></code> folder, so we don’t have to give the full path.</p>
 <blockquote>
-<div><p>Note also how we use <code class="docutils literal notranslate"><span class="pre">.</span></code> instead of <code class="docutils literal notranslate"><span class="pre">/</span></code> (or <code class="docutils literal notranslate"><span class="pre">\</span></code> on Windows). This is a so-called “Python path”. In a Python-path,
-you separate the parts of the path with <code class="docutils literal notranslate"><span class="pre">.</span></code> and skip the <code class="docutils literal notranslate"><span class="pre">.py</span></code> file-ending. Importantly, it also allows you to point to
-Python code <em>inside</em> files, like the <code class="docutils literal notranslate"><span class="pre">BodyFunctions</span></code> class inside <code class="docutils literal notranslate"><span class="pre">bodyfunctions.py</span></code> (we’ll get to classes later).
-These “Python-paths” are used extensively throughout Evennia.</p>
+<div><p>Note also how we use <code class="docutils literal notranslate"><span class="pre">.</span></code> instead of <code class="docutils literal notranslate"><span class="pre">/</span></code> (or <code class="docutils literal notranslate"><span class="pre">\</span></code> on Windows). This is a so-called “Python path”. In a Python-path, &gt; you separate the parts of the path with <code class="docutils literal notranslate"><span class="pre">.</span></code> and skip the <code class="docutils literal notranslate"><span class="pre">.py</span></code> file-ending. Importantly, it also allows you to point to Python code <em>inside</em> files, like the <code class="docutils literal notranslate"><span class="pre">BodyFunctions</span></code> class inside <code class="docutils literal notranslate"><span class="pre">bodyfunctions.py</span></code> (we’ll get to classes later). These “Python-paths” are used extensively throughout Evennia.</p>
 </div></blockquote>
 <p>Wait a while and you will notice yourself starting making random observations …</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>script self
 </pre></div>
 </div>
-<p>This will show details about scripts on yourself (also <code class="docutils literal notranslate"><span class="pre">examine</span></code> works). You will see how long it is
-until it “fires” next. Don’t be alarmed if nothing happens when the countdown reaches zero - this
-particular script has a randomizer to determine if it will say something or not. So you will not see
-output every time it fires.</p>
+<p>This will show details about scripts on yourself (also <code class="docutils literal notranslate"><span class="pre">examine</span></code> works). You will see how long it is until it “fires” next. Don’t be alarmed if nothing happens when the countdown reaches zero - this particular script has a randomizer to determine if it will say something or not. So you will not see output every time it fires.</p>
 <p>When you are tired of your character’s “insights”, kill the script with</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>script/stop self = tutorials.bodyfunctions.BodyFunctions
 </pre></div>
 </div>
-<p>You create your own scripts in Python, outside the game; the path you give to <code class="docutils literal notranslate"><span class="pre">script</span></code> is literally
-the Python path to your script file. The <a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a> page explains more details.</p>
+<p>You create your own scripts in Python, outside the game; the path you give to <code class="docutils literal notranslate"><span class="pre">script</span></code> is literally the Python path to your script file. The <a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a> page explains more details.</p>
 </section>
 <section id="pushing-your-buttons">
 <h2><span class="section-number">1.6. </span>Pushing Your Buttons<a class="headerlink" href="#pushing-your-buttons" title="Permalink to this headline">¶</a></h2>
-<p>If we get back to the box we made, there is only so much fun you can have with it at this point. It’s
-just a dumb generic object. If you renamed it to <code class="docutils literal notranslate"><span class="pre">stone</span></code> and changed its description, noone would be
-the wiser. However, with the combined use of custom <a class="reference internal" href="../../../Components/Typeclasses.html"><span class="doc std std-doc">Typeclasses</span></a>, <a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a>
+<p>If we get back to the box we made, there is only so much fun you can have with it at this point. It’s just a dumb generic object. If you renamed it to <code class="docutils literal notranslate"><span class="pre">stone</span></code> and changed its description, noone would be the wiser. However, with the combined use of custom <a class="reference internal" href="../../../Components/Typeclasses.html"><span class="doc std std-doc">Typeclasses</span></a>, <a class="reference internal" href="../../../Components/Scripts.html"><span class="doc std std-doc">Scripts</span></a>
 and object-based <a class="reference internal" href="../../../Components/Commands.html"><span class="doc std std-doc">Commands</span></a>, you could expand it and other items to be as unique, complex
 and interactive as you want.</p>
-<p>Let’s take an example. So far we have only created objects that use the default object typeclass
-named simply <code class="docutils literal notranslate"><span class="pre">Object</span></code>. Let’s create an object that is a little more interesting. Under
-<code class="docutils literal notranslate"><span class="pre">evennia/contrib/tutorial_examples</span></code> there is a module <code class="docutils literal notranslate"><span class="pre">red_button.py</span></code>.  It contains the enigmatic
-<code class="docutils literal notranslate"><span class="pre">RedButton</span></code> class.</p>
+<p>Let’s take an example. So far we have only created objects that use the default object typeclass named simply <code class="docutils literal notranslate"><span class="pre">Object</span></code>. Let’s create an object that is a little more interesting. Under
+<code class="docutils literal notranslate"><span class="pre">evennia/contrib/tutorials</span></code> there is a module <code class="docutils literal notranslate"><span class="pre">red_button.py</span></code>.  It contains the enigmatic <code class="docutils literal notranslate"><span class="pre">RedButton</span></code> class.</p>
 <p>Let’s make us one of <em>those</em>!</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>create/drop button:tutorials.red_button.RedButton
 </pre></div>
 </div>
-<p>The same way we did with the Script Earler, we specify a “Python-path” to the Python code we want Evennia
-to use for creating the object. There you go - one red button.</p>
-<p>The RedButton is an example object intended to show off a few of Evennia’s features. You will find
-that the <a class="reference internal" href="../../../Components/Typeclasses.html"><span class="doc std std-doc">Typeclass</span></a> and <a class="reference internal" href="../../../Components/Commands.html"><span class="doc std std-doc">Commands</span></a> controlling it are
-inside <a class="reference internal" href="../../../api/evennia.contrib.tutorials.red_button.html"><span class="doc std std-doc">evennia/contrib/tutorials/red_button</span></a></p>
+<p>The same way we did with the Script Earler, we specify a “Python-path” to the Python code we want Evennia to use for creating the object. There you go - one red button.</p>
+<p>The RedButton is an example object intended to show off a few of Evennia’s features. You will find that the <a class="reference internal" href="../../../Components/Typeclasses.html"><span class="doc std std-doc">Typeclass</span></a> and <a class="reference internal" href="../../../Components/Commands.html"><span class="doc std std-doc">Commands</span></a> controlling it are inside <a class="reference internal" href="../../../api/evennia.contrib.tutorials.red_button.html"><span class="doc std std-doc">evennia/contrib/tutorials/red_button</span></a></p>
 <p>If you wait for a while (make sure you dropped it!) the button will blink invitingly.</p>
 <p>Why don’t you try to push it …?</p>
 <p>Surely a big red button is meant to be pushed.</p>
@@ -319,31 +272,22 @@ inside <a class="reference internal" href="../../../api/evennia.contrib.tutorial
 </section>
 <section id="making-yourself-a-house">
 <h2><span class="section-number">1.7. </span>Making Yourself a House<a class="headerlink" href="#making-yourself-a-house" title="Permalink to this headline">¶</a></h2>
-<p>The main command for shaping the game world is <code class="docutils literal notranslate"><span class="pre">dig</span></code>. For example, if you are standing in Limbo, you
-can dig a route to your new house location like this:</p>
+<p>The main command for shaping the game world is <code class="docutils literal notranslate"><span class="pre">dig</span></code>. For example, if you are standing in Limbo, you can dig a route to your new house location like this:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>dig house = large red door;door;in,to the outside;out
 </pre></div>
 </div>
-<p>This will create a new room named ‘house’. Spaces at the start/end of names and aliases are ignored
-so you could put more air if you wanted.  This call will directly create an exit from your current
-location named ‘large red door’ and a corresponding exit named ‘to the outside’ in the house room
-leading back to Limbo. We also define a few aliases to those exits, so people don’t have to write
-the full thing all the time.</p>
-<p>If you wanted to use normal compass directions (north, west, southwest etc), you could do that with
-<code class="docutils literal notranslate"><span class="pre">dig</span></code> too. But Evennia also has a limited version of <code class="docutils literal notranslate"><span class="pre">dig</span></code> that helps for compass directions (and
-also up/down and in/out). It’s called <code class="docutils literal notranslate"><span class="pre">tunnel</span></code>:</p>
+<p>This will create a new room named ‘house’. Spaces at the start/end of names and aliases are ignored so you could put more air if you wanted.  This call will directly create an exit from your current location named ‘large red door’ and a corresponding exit named ‘to the outside’ in the house room leading back to Limbo. We also define a few aliases to those exits, so people don’t have to write the full thing all the time.</p>
+<p>If you wanted to use normal compass directions (north, west, southwest etc), you could do that with <code class="docutils literal notranslate"><span class="pre">dig</span></code> too. But Evennia also has a limited version of <code class="docutils literal notranslate"><span class="pre">dig</span></code> that helps for compass directions (and also up/down and in/out). It’s called <code class="docutils literal notranslate"><span class="pre">tunnel</span></code>:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>tunnel sw = cliff
 </pre></div>
 </div>
-<p>This will create a new room “cliff” with an exit “southwest” leading there and a path “northeast”
-leading back from the cliff to your current location.</p>
+<p>This will create a new room “cliff” with an exit “southwest” leading there and a path “northeast” leading back from the cliff to your current location.</p>
 <p>You can create new exits from where you are, using the <code class="docutils literal notranslate"><span class="pre">open</span></code> command:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>open north;n = house
 </pre></div>
 </div>
 <p>This opens an exit <code class="docutils literal notranslate"><span class="pre">north</span></code> (with an alias <code class="docutils literal notranslate"><span class="pre">n</span></code>) to the previously created room <code class="docutils literal notranslate"><span class="pre">house</span></code>.</p>
-<p>If you have many rooms named <code class="docutils literal notranslate"><span class="pre">house</span></code> you will get a list of matches and have to select which one you
-want to link to.</p>
+<p>If you have many rooms named <code class="docutils literal notranslate"><span class="pre">house</span></code> you will get a list of matches and have to select which one you want to link to.</p>
 <p>Follow the north exit to your ‘house’ or <code class="docutils literal notranslate"><span class="pre">teleport</span></code> to it:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>north
 </pre></div>
@@ -360,8 +304,7 @@ want to link to.</p>
 </section>
 <section id="reshuffling-the-world">
 <h2><span class="section-number">1.8. </span>Reshuffling the World<a class="headerlink" href="#reshuffling-the-world" title="Permalink to this headline">¶</a></h2>
-<p>You can find things using the <code class="docutils literal notranslate"><span class="pre">find</span></code> command. Assuming you are back at <code class="docutils literal notranslate"><span class="pre">Limbo</span></code>, let’s teleport the
-<em>large box</em> to our house.</p>
+<p>You can find things using the <code class="docutils literal notranslate"><span class="pre">find</span></code> command. Assuming you are back at <code class="docutils literal notranslate"><span class="pre">Limbo</span></code>, let’s teleport the <em>large box</em> to our house.</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>teleport box = house
     very large box is leaving Limbo, heading for house.
     Teleported very large box -&gt; house.
@@ -373,25 +316,20 @@ want to link to.</p>
     very large box(#8) - src.objects.objects.Object
 </pre></div>
 </div>
-<p>Knowing the <code class="docutils literal notranslate"><span class="pre">#dbref</span></code> of the box (#8 in this example), you can grab the box and get it back here
-without actually yourself going to <code class="docutils literal notranslate"><span class="pre">house</span></code> first:</p>
+<p>Knowing the <code class="docutils literal notranslate"><span class="pre">#dbref</span></code> of the box (#8 in this example), you can grab the box and get it back here without actually yourself going to <code class="docutils literal notranslate"><span class="pre">house</span></code> first:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>teleport #8 = here
 </pre></div>
 </div>
-<p>As mentioned, <code class="docutils literal notranslate"><span class="pre">here</span></code> is an alias for ‘your current location’. The box should now be back in Limbo with you.</p>
-<p>We are getting tired of the box. Let’s destroy it.</p>
+<p>As mentioned, <code class="docutils literal notranslate"><span class="pre">here</span></code> is an alias for ‘your current location’. The box should now be back in Limbo with you. We are getting tired of the box. Let’s destroy it.</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>destroy box
 </pre></div>
 </div>
 <p>It will ask you for confirmation. Once you give it, the box will be gone.</p>
-<p>You can destroy many objects in one go by giving a comma-separated list of objects (or a range
-of #dbrefs, if they are not in the same location) to the command.</p>
+<p>You can destroy many objects in one go by giving a comma-separated list of objects (or a range of #dbrefs, if they are not in the same location) to the command.</p>
 </section>
 <section id="adding-a-help-entry">
 <h2><span class="section-number">1.9. </span>Adding a Help Entry<a class="headerlink" href="#adding-a-help-entry" title="Permalink to this headline">¶</a></h2>
-<p>The Command-help is something you modify in Python code. We’ll get to that when we get to how to
-add Commands. But you can also add regular help entries, for example to explain something about
-the history of your game world:</p>
+<p>The Command-help is something you modify in Python code. We’ll get to that when we get to how to add Commands. But you can also add regular help entries, for example to explain something about the history of your game world:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>sethelp History = At the dawn of time ...
 </pre></div>
 </div>
@@ -399,8 +337,7 @@ the history of your game world:</p>
 </section>
 <section id="adding-a-world">
 <h2><span class="section-number">1.10. </span>Adding a World<a class="headerlink" href="#adding-a-world" title="Permalink to this headline">¶</a></h2>
-<p>After this brief introduction to building and using in-game commands you may be ready to see a more fleshed-out
-example. Evennia comes with a tutorial world for you to explore. We will try that out in the next lesson.</p>
+<p>After this brief introduction to building and using in-game commands you may be ready to see a more fleshed-out example. Evennia comes with a tutorial world for you to explore. We will try that out in the next lesson.</p>
 </section>
 </section>