@@ -107,7 +107,7 @@ will infer the timezone in the following order.
107107
108108#### Disambiguating Ambiguous Timezone Conversions
109109
110- Sometimes, when youre converting a datetime from one timezone to another, there
110+ Sometimes, when you're converting a datetime from one timezone to another, there
111111are potentially two different results if the conversion happens to land on in a
112112timezone that's in the middle of a Daylight Saving conversion. For example,
113113converting "11-Nov-2013 1:00: am " in "America/New York" to "GMT" could be both
@@ -536,7 +536,7 @@ qdate:between(qdate:add_minutes(-15), Date, qdate:add_minutes(15)).
536536
537537% % But, you don't have to: if that's a common format you use in your
538538% % application, you can register your format with the `qdate` server, and then
539- % % easiy refer to that format by its key.
539+ % % easily refer to that format by its key.
540540
541541% % So let's take that format and register it
54254216 > qdate :register_format (longdate , " l, F jS, Y g:i A T" ).
@@ -720,7 +720,7 @@ the week" calculation. This has three forms, specifically:
720720 7=Sunday).
721721 + ` beginning_week(DayOfWeek, Date) ` - Calculates the beginning of the week
722722 based on the provided ` DayOfWeek ` . Valid values for DayOfWeek are the
723- integers 1-7 or the atom verions of the days of the week. Specifically:
723+ integers 1-7 or the atom versions of the days of the week. Specifically:
724724
725725 * Monday: ` 1 | monday | mon `
726726 * Tuesday: ` 2 | tuesday | tue `
0 commit comments