Publish pull/19 (built from linux-kernel-labs/linux#19)

pull/19/_sources/lectures/intro.rst.txt

@@ -69,10 +69,10 @@ protection or to virtual address spaces associated with either the
 kernel or user applications.
 
 Grossly simplifying, the kernel space is the memory area that is
-reserved to the kernel while user space is the memory area
-reserved to a particular user process. The kernel space is accessed
-protected so that user applications can not access it directly, while
-user space can be directly accessed from code running in kernel mode.
+reserved to the kernel while user space is the memory area reserved to
+a particular user process. The kernel space is accessed protected so
+that user applications can not access it directly, while user space
+can be directly accessed from code running in kernel mode.
 
 
 Typical operating system architecture

pull/19/_sources/lectures/syscalls.rst.txt

@@ -326,8 +326,8 @@ crafted:
    :inline-contents: True
    :level: 2
 
-   * The exact instructions that access user space are recorded
-     in a table (exception table)
+   * The exact instructions that access user space are recorded in a
+     table (exception table)
 
    * When a page fault occurs the faulting address is checked against
      this table

pull/19/lectures/intro.html

@@ -251,10 +251,10 @@ <h3>User vs Kernel<a class="headerlink" href="#user-vs-kernel" title="Permalink
 protection or to virtual address spaces associated with either the
 kernel or user applications.</p>
 <p>Grossly simplifying, the kernel space is the memory area that is
-reserved to the kernel while user space is the memory area
-reserved to a particular user process. The kernel space is accessed
-protected so that user applications can not access it directly, while
-user space can be directly accessed from code running in kernel mode.</p>
+reserved to the kernel while user space is the memory area reserved to
+a particular user process. The kernel space is accessed protected so
+that user applications can not access it directly, while user space
+can be directly accessed from code running in kernel mode.</p>
 </div>
 <div class="section" id="typical-operating-system-architecture">
 <h3>Typical operating system architecture<a class="headerlink" href="#typical-operating-system-architecture" title="Permalink to this headline">¶</a></h3>

pull/19/lectures/syscalls-slides.html

@@ -274,8 +274,8 @@ <h2>Page fault handling</h2>
 <h2>Marking kernel code that accesses user space</h2>
 
 <ul class="simple">
-<li>The exact instructions that access user space are recorded
-in a table (exception table)</li>
+<li>The exact instructions that access user space are recorded in a
+table (exception table)</li>
 <li>When a page fault occurs the faulting address is checked against
 this table</li>
 </ul>

pull/19/lectures/syscalls.html

@@ -347,8 +347,8 @@ <h3>System call parameters handling<a class="headerlink" href="#system-call-para
 <code class="xref c c-func docutils literal"><span class="pre">copy_to_user()</span></code>) to accesses user space that are specially
 crafted:</p>
 <ul class="admonition-marking-kernel-code-that-accesses-user-space simple">
-<li>The exact instructions that access user space are recorded
-in a table (exception table)</li>
+<li>The exact instructions that access user space are recorded in a
+table (exception table)</li>
 <li>When a page fault occurs the faulting address is checked against
 this table</li>
 </ul>