From eb4867791506d7feb1da45ae1dbee05eb286e95e Mon Sep 17 00:00:00 2001
From: Richard Brooksby <rb@ravenbrook.com>
Date: Thu, 18 Feb 2016 21:00:38 +0000
Subject: [PATCH] Fixing design documentation of mutatorfaultcontextscan.

Copied from Perforce
 Change: 189314
 ServerID: perforce.ravenbrook.com
---
 mps/design/prmc.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/mps/design/prmc.txt b/mps/design/prmc.txt
index 0822e709527..43d24a34ec4 100644
--- a/mps/design/prmc.txt
+++ b/mps/design/prmc.txt
@@ -104,11 +104,11 @@ instruction which was caused the fault to be re-executed. Return
 This function is only called if ``ProtCanStepInstruction(context)``
 returned ``TRUE``.
 
-``Res MutatorFaultContextScan(ScanState ss, MutatorFaultContext context)``
+``Res MutatorFaultContextScan(ScanState ss, MutatorFaultContext mfc, mps_area_scan_t scan, void *closure, size_t closure_size)``
 
 _`.if.context.scan`: Scan all roots found in ``context`` using the
-given scan state (typically by calling ``TraceScanAreaTagged()``), and
-return the result code from the scanner.
+given scan state by calling ``scan``, and return the result code from
+the scanner.
 
 ``Addr MutatorFaultContextSP(MutatorFaultContext context)``