From 302e20333b5da7f5f5166264c54bee7e3add6652 Mon Sep 17 00:00:00 2001 From: Daniel Bovensiepen Date: Wed, 2 Oct 2013 00:50:55 +0800 Subject: Improve Grammar of Documentation --- src/gc.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'src/gc.c') diff --git a/src/gc.c b/src/gc.c index 16d187e30..361024af3 100644 --- a/src/gc.c +++ b/src/gc.c @@ -28,11 +28,11 @@ mruby's GC is Tri-color Incremental GC with Mark & Sweep. Algorithm details are omitted. - Instead, the part about the implementation described below. + Instead, the implementation part is described below. == Object's Color - Each object to be painted in three colors. + Each object can be painted in three colors: * White - Unmarked. * Gray - Marked, But the child objects are unmarked. @@ -68,9 +68,9 @@ == Write Barrier - mruby implementer, C extension library writer must write a write + mruby implementer and C extension library writer must write a write barrier when writing a pointer to an object on object's field. - Two different write barrier: + Two different write barrier are available: * mrb_field_write_barrier * mrb_write_barrier @@ -88,7 +88,7 @@ * Major GC - same as a full regular GC cycle. - the difference between "tranditional" generational GC is that, the major GC + The difference to a "traditional" generational GC is, that the major GC in mruby is triggered incrementally in a tri-color manner. -- cgit v1.2.3