X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fuserprog.texi;h=64d429fd1b38dd3d89596dff86dc1f406a6066b1;hb=98c2fc1ab7d395bb92cf4a57233fe432539d26a9;hp=5f270e1fe74ac6a86ec17072050dd946843e70f6;hpb=f2e153aa439ac3ebb9070dc2e9ac5f7c9ef2fd93;p=pintos-anon

diff --git a/doc/userprog.texi b/doc/userprog.texi
index 5f270e1..64d429f 100644
--- a/doc/userprog.texi
+++ b/doc/userprog.texi
@@ -477,7 +477,7 @@ e.g.@: @samp{example 1 2 3 4: 0}.
 @end enumerate
 
 @node 80x86 Calling Convention
-@appendixsec 80@var{x}86 Calling Convention
+@section 80@var{x}86 Calling Convention
 
 What follows is a quick and dirty discussion of the 80@var{x}86
 calling convention.  Some of the basics should be familiar from CS
@@ -627,7 +627,7 @@ address space, in the page just below virtual address @code{PHYS_BASE}
 (defined in @file{threads/mmu.h}).
 
 @node System Calls
-@appendixsec System Calls
+@section System Calls
 
 We have already been dealing with one way that the operating system
 can regain control from a user program: interrupts from timers and I/O