Skip to content

Commit dbdbb17

Browse files
committed
Fix typos in documentation
1 parent 825cbda commit dbdbb17

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This way, more people get a chance to take a look at the code before the public
3333
## Quickstart example
3434

3535
TSV (Tab-Separated Values) is a very simple text-based format for storing a
36-
large number of (uniform) records, such as a list of temparature records or log
36+
large number of (uniform) records, such as a list of temperature records or log
3737
entries.
3838

3939
```
@@ -94,11 +94,11 @@ commonly Character-Separated Values), it is more than just a small variation.
9494

9595
* TSV always uses a tab stop (`\t`) as a delimiter between fields, CSV uses a
9696
comma (`,`) by default, but some applications use variations such as a
97-
semicolon (`;`) or other application-dependant characters (this is
97+
semicolon (`;`) or other application-dependent characters (this is
9898
particularly common for systems in Europe (and elsewhere) that use a comma as
9999
decimal separator).
100100
* TSV always uses field names in the first row, CSV allows for optional field
101-
names (which is application-dependant).
101+
names (which is application-dependent).
102102
* TSV always uses the same number of fields for all rows, CSV allows for rows
103103
with different number of fields (though this is rarely used).
104104
* CSV requires quoting
@@ -113,7 +113,7 @@ TSV files are commonly limited to only ASCII characters for best interoperabilit
113113
However, many legacy TSV files often use ISO 8859-1 encoding or some other
114114
variant. Newer TSV files are usually best saved as UTF-8 and may thus also
115115
contain special characters from the Unicode range. The text-encoding is usually
116-
application-dependant, so your best bet would be to convert to (or assume) UTF-8
116+
application-dependent, so your best bet would be to convert to (or assume) UTF-8
117117
consistently.
118118

119119
Despite its shortcomings, TSV is widely used and this is unlikely to change any
@@ -182,7 +182,7 @@ it will emit an `error` event and then `close` the input stream:
182182
183183
```php
184184
$stream->on('error', function (Exception $error) {
185-
// an error occured, stream will close next
185+
// an error occurred, stream will close next
186186
});
187187
```
188188
@@ -255,7 +255,7 @@ it will emit an `error` event and then `close` the input stream:
255255
256256
```php
257257
$stream->on('error', function (Exception $error) {
258-
// an error occured, stream will close next
258+
// an error occurred, stream will close next
259259
});
260260
```
261261

examples/users.tsv

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,5 @@ fifth 1973-01-01 5.1.1.1
77
sixth 1962-01-01 6.1.1.1
88
seventh 1951-01-01 7.1.1.1
99
eighth 1940-01-01 8.1.1.1
10-
nineth 1939-01-01 9.1.1.1
10+
ninth 1939-01-01 9.1.1.1
1111
tenth 1928-01-01

0 commit comments

Comments
 (0)