Cosmetic changes for better HTML output.

2 files changed, 9 insertions, 9 deletions

diff --git a/share/doc/papers/newvm/1.t b/share/doc/papers/newvm/1.t
index 036adeeb2319..7b66674085a3 100644
--- a/share/doc/papers/newvm/1.t
+++ b/share/doc/papers/newvm/1.t
@@ -43,7 +43,7 @@ This section of the paper describes the current design,
 points out the current technological trends,
 and attempts to define the new design considerations that should
 be taken into account in a new virtual memory design.
-.SH
+.NH 2
 Implementation of 4.3BSD virtual memory
 .PP
 All Berkeley Software Distributions through 4.3BSD
@@ -71,7 +71,7 @@ to contain newly faulted pages.
 If a previously accessed page that has been pushed to swap is once
 again used, a free page is reallocated and filled from the swap area
 [Babaoglu79], [Someren84].
-.SH
+.NH 2
 Design assumptions for 4.3BSD virtual memory
 .PP
 The design criteria for the current virtual memory implementation
@@ -110,7 +110,7 @@ Given the high cost of memory there was little incentive to have
 the kernel keep track of the contents of the swap area once a process
 exited since it could almost as easily and quickly be reread from the
 file system.
-.SH
+.NH 2
 New influences
 .PP
 In the ten years since the current virtual memory system was designed,
@@ -190,7 +190,7 @@ User Interface
 This section outlines our new virtual memory interface as it is
 currently envisioned.
 The details of the system call interface are contained in Appendix A.
-.SH
+.NH 2
 Regions
 .PP
 The virtual memory interface is designed to support both large,
@@ -259,7 +259,7 @@ processes that wish to attach to the region.
 Such a descriptor may be bound into the UNIX file system
 name space so that other processes can find it just as
 they would with a mapped file.
-.SH
+.NH 2
 Shared memory as high speed interprocess communication
 .PP
 The primary use envisioned for shared memory is to
diff --git a/share/doc/papers/newvm/a.t b/share/doc/papers/newvm/a.t
index 7248e25e991e..5a9bac4494ec 100644
--- a/share/doc/papers/newvm/a.t
+++ b/share/doc/papers/newvm/a.t
@@ -36,7 +36,7 @@
 .ne 2i
 .NH
 Appendix A \- Virtual Memory Interface
-.SH
+.NH 2
 Mapping pages
 .PP
 The system supports sharing of data between processes
@@ -148,7 +148,7 @@ caddr_t addr; int len;
 This call deletes the mappings for the specified address range,
 and causes further references to addresses within the range
 to generate invalid memory references.
-.SH
+.NH 2
 Page protection control
 .PP
 A process can control the protection of pages using the call
@@ -159,7 +159,7 @@ caddr_t addr; int len, prot;
 This call changes the specified pages to have protection \fIprot\fP\|.
 Not all implementations will guarantee protection on a page basis;
 the granularity of protection changes may be as large as an entire region.
-.SH
+.NH 2
 Giving and getting advice
 .PP
 A process that has knowledge of its memory behavior may
@@ -188,7 +188,7 @@ caddr_t addr; int len; result char *vec;
 Here the current core residency of the pages is returned
 in the character array \fIvec\fP, with a value of 1 meaning
 that the page is in-core.
-.SH
+.NH 2
 Synchronization primitives
 .PP
 Primitives are provided for synchronization using semaphores in shared memory.