-@node Managing the Segment Table
-@subsection Managing the Segment Table
-
-The @dfn{segment table} supplements the page table with additional data
-about each page. It is required because of the limitations imposed by
-the page table's format. Such a supplementary data structure is often
-called a ``page table'' also; we call it a segment table to avoid
-confusion.
-
-The segment table is used for at least two purposes. Most importantly,
-on a page fault, the kernel looks up the virtual page that faulted in
-the segment table to find out what data should be there. Second, the
-kernel consults the segment table when a process terminates, to decide
-what resources to free.
-
-You may organize the segment table as you wish. There are at least two
-basic approaches to its organization: in terms of segments or in terms
-of pages. Optionally, you may use the page table as part of your
-segment table design. You will have to modify the Pintos page table
-implementation in @file{pagedir.c} to do so. We recommend this approach
-for advanced students only. @xref{Page Table Entry Format}, for more
-information.
-
-The most important user of the segment table is the page fault handler.
-In project 2, a page fault always indicated a bug in the kernel or a
-user program. In project 3, this is no longer true. Now, a page fault
-might only indicate that the page must be brought in from a file or
-swap. You will have to implement a more sophisticated page fault
-handler to handle these cases. Your page fault handler, which you
+@node Managing the Supplemental Page Table
+@subsection Managing the Supplemental Page Table
+
+The @dfn{supplemental page table} supplements the page table with
+additional data about each page. It is needed because of the
+limitations imposed by the page table's format. Such a data structure
+is often called a ``page table'' also; we add the word ``supplemental''
+to reduce confusion.
+
+The supplemental page table is used for at least two purposes. Most
+importantly, on a page fault, the kernel looks up the virtual page that
+faulted in the supplemental page table to find out what data should be
+there. Second, the kernel consults the supplemental page table when a
+process terminates, to decide what resources to free.
+
+You may organize the supplemental page table as you wish. There are at
+least two basic approaches to its organization: in terms of segments or
+in terms of pages. Optionally, you may use the page table itself as an
+index to track the members of the supplemental page table. You will
+have to modify the Pintos page table implementation in @file{pagedir.c}
+to do so. We recommend this approach for advanced students only.
+@xref{Page Table Entry Format}, for more information.
+
+The most important user of the supplemental page table is the page fault
+handler. In project 2, a page fault always indicated a bug in the
+kernel or a user program. In project 3, this is no longer true. Now, a
+page fault might only indicate that the page must be brought in from a
+file or swap. You will have to implement a more sophisticated page
+fault handler to handle these cases. Your page fault handler, which you