[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [6391] Improve documentation

From: Greg Chicares
Subject: [lmi-commits] [6391] Improve documentation
Date: Sat, 07 Nov 2015 13:22:18 +0000

Revision: 6391
Author:   chicares
Date:     2015-11-07 13:22:17 +0000 (Sat, 07 Nov 2015)
Log Message:
Improve documentation

Modified Paths:

Modified: lmi/trunk/input_harmonization.cpp
--- lmi/trunk/input_harmonization.cpp   2015-11-06 22:05:23 UTC (rev 6390)
+++ lmi/trunk/input_harmonization.cpp   2015-11-07 13:22:17 UTC (rev 6391)
@@ -1087,10 +1087,10 @@
 /// next monthiversary is credited, as one combined atomic operation.
 /// Therefore, any inforce data must be given as of a monthiversary
 /// date, after interest has been credited for the month just ending,
-/// and immediately before a monthiversary deduction. (Admin systems
+/// and immediately before the monthiversary deduction. (Admin systems
 /// might reckon this point to occur one second after midnight on a
 /// monthiversary date, or one second before midnight on the preceding
-/// day, but the InforceAsOfDate they provide to lmi must follow lmi's
+/// day; but the InforceAsOfDate they provide to lmi must follow lmi's
 /// reckoning: it must be the monthiversary date.)
 /// Preconditions: Neither EffectiveDate nor LastMaterialChangeDate
@@ -1112,7 +1112,7 @@
 /// because of the quantization of illustration time, so inforce year
 /// and inforce month cannot both equal zero. An exception is thrown
 /// if this postcondition is violated because new business and inforce
-/// illustrations differ categorically: they regulated differently,
+/// illustrations differ categorically: they're regulated differently,
 /// and they're calculated differently (e.g., input inforce values
 /// must be taken into account for inforce, but disregarded (or
 /// asserted to be zero) for new business).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]