RE: #213 - wording

Coding standards

Author: u01jmg3

README.md

@@ -11,7 +11,7 @@
  - PHP 5 (≥ 5.3.0)
  - [Valid ICS](https://icalendar.org/validator.html) (`.ics`, `.ical`, `.ifb`) file
  - [IANA](https://www.iana.org/time-zones), [Unicode CLDR](http://cldr.unicode.org/translation/timezones) or [Windows](https://support.microsoft.com/en-ca/help/973627/microsoft-time-zone-index-values) Time Zones
-   - Windows Time Zones will need the `$replaceWindowsTimeZoneIds = true` configuration
+   - If Windows time zones are present you will need to set `$replaceWindowsTimeZoneIds` to `true`
 
 ### Setup
 
@@ -66,14 +66,15 @@
 
 ---
 
-## On parsing iCal
-Parsing [iCal/iCalendar/ICS](https://en.wikipedia.org/wiki/ICalendar) resources poses several challenges. One is that
-the specification is a moving target; the original RFC was updated four times in ten years. The other is that vendors
+## When Parsing an iCal Feed
+
+Parsing [iCal/iCalendar/ICS](https://en.wikipedia.org/wiki/ICalendar) resources can pose several challenges. One challenge is that
+the specification is a moving target; the original RFC has only been updated four times in ten years. The other challenge is that vendors
 were both liberal (read: creative) in interpreting the specification and productive implementing proprietary extensions.
 
 However, what impedes efficient parsing most directly are recurrence rules for events. This library parses the original
 calendar into an easy to work with memory model. This requires that each recurring event is expanded or exploded. Hence,
-a single event that occurs daily will generate a new event instance for every day when this parser processes the
+a single event that occurs daily will generate a new event instance for each day as this parser processes the
 calendar ([`$defaultSpan`](#variables) limits this). To get an idea how this is done take a look at the
 [call graph](https://user-images.githubusercontent.com/624195/45904641-f3cd0a80-bded-11e8-925f-7bcee04b8575.png).
 
@@ -82,24 +83,24 @@ large calendars tend to get huge when exploded i.e. with all their recurrence ru
 old calendars do not remove past events as they get fatter and fatter every year.
 
 This limitation is particularly painful if you only need a window into the original calendar. It seems wasteful to parse
-the entire fully exploded calendar into memory if you later are going to call the 
+the entire fully exploded calendar into memory if you later are going to call the
 [`eventsFromInterval()` or `eventsFromRange()`](#methods) on it.
 
-In late 2018 [#190](https://github.com/u01jmg3/ics-parser/pull/190) added the option to drop all events outside a given 
-range very early in the parse process at the cost of some precision (timezone calculations not done at that point). This 
-massively reduces the total time for parsing a calendar. Same goes for memory consumption of course. Precondition is that 
+In late 2018 [#190](https://github.com/u01jmg3/ics-parser/pull/190) added the option to drop all events outside a given
+range very early in the parsing process at the cost of some precision (time zone calculations are not calculated at that point). This
+massively reduces the total time for parsing a calendar. The same goes for memory consumption. The precondition is that
 you know upfront that you don't care about events outside a given range.
 
-Let's say your are only interested in events from yesterday, today and tomorrow. To compensate for the fact that the
-tricky timezone transformations and calculations have not been executed yet by the time the parser has to decide whether
-to keep or drop an event you tell it to filter for **+-2d** instead of +-1d. Once it is done you would then call
+Let's say you are only interested in events from yesterday, today and tomorrow. To compensate for the fact that the
+tricky time zone transformations and calculations have not been executed yet by the time the parser has to decide whether
+to keep or drop an event you can set it to filter for **+-2d** instead of +-1d. Once it is done you would then call
 `eventsFromRange()` with +-1d to get precisely the events in the window you are interested in. That is what the variables
 [`$filterDaysBefore` and `$filterDaysAfter`]((#variables)) are for.
 
-In Q1 2019 [#213](https://github.com/u01jmg3/ics-parser/pull/213) further improved the performance by immediately 
-dropping _non-recurring_ events once parsed if they are outside that fuzzy window. This greatly reduces the maximum 
-memory consumption for large calendars. PHP by default does not allocate more than 128MB heap and would otherwise crash 
-with `Fatal error: Allowed memory size of 134217728 bytes exhausted`. It goes without saying that recurring events first 
+In Q1 2019 [#213](https://github.com/u01jmg3/ics-parser/pull/213) further improved the performance by immediately
+dropping _non-recurring_ events once parsed if they are outside that fuzzy window. This greatly reduces the maximum
+memory consumption for large calendars. PHP by default does not allocate more than 128MB heap and would otherwise crash
+with `Fatal error: Allowed memory size of 134217728 bytes exhausted`. It goes without saying that recurring events first
 need to be evaluated before non-fitting events can be dropped.
 
 ---

src/ICal/ICal.php

@@ -645,8 +645,9 @@ protected function initLines(array $lines)
                             if ($this->shouldFilterByWindow) {
                                 $this->removeLastEventIfOutsideWindowAndNonRecurring();
                             }
+
                             $component = 'VCALENDAR';
-                        break;
+                            break;
 
                         default:
                             $this->addCalendarComponentWithKeyAndValue($component, $keyword, $value);
@@ -688,14 +689,13 @@ protected function initLines(array $lines)
      * Removes the last event (i.e. most recently parsed) if its start date is outside the window spanned by
      * `$windowMinTimestamp` / `$windowMaxTimestamp`.
      *
-     * @throws \Exception
+     * @return void
      */
     protected function removeLastEventIfOutsideWindowAndNonRecurring()
     {
         $events = $this->cal['VEVENT'];
 
         if (!empty($events)) {
-
             $lastIndex = sizeof($events) - 1;
             $lastEvent = $events[$lastIndex];
 
@@ -721,6 +721,7 @@ protected function reduceEventsToMinMaxRange()
             foreach ($events as $key => $anEvent) {
                 if ($this->isEventStartOutsideWindow($anEvent)) {
                     $this->eventCount--;
+
                     unset($events[$key]);
 
                     continue;
@@ -737,7 +738,6 @@ protected function reduceEventsToMinMaxRange()
      *
      * @param  array $event
      * @return boolean
-     * @throws \Exception
      */
     protected function isEventStartOutsideWindow(array $event)
     {