aboutsummaryrefslogtreecommitdiffhomepage
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorSergey M․ <[email protected]>2016-10-31 01:36:53 +0700
committerSergey M․ <[email protected]>2016-10-31 01:36:53 +0700
commit2c6da7df4a4d69ec933688e3c53795fd3436a1c6 (patch)
treed92c3afb0b91c88e6fde8277d099caf49e3b5837 /CONTRIBUTING.md
parent7e7a028aa4108f5ce455fda88dfdcee13b3b7578 (diff)
downloadyoutube-dl-2c6da7df4a4d69ec933688e3c53795fd3436a1c6.tar.gz
youtube-dl-2c6da7df4a4d69ec933688e3c53795fd3436a1c6.zip
release 2016.10.312016.10.31
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 29f52cbe8..0b5a5c1f8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -245,7 +245,7 @@ Say `meta` from the previous example has a `title` and you are about to extract
title = meta['title']
```
-If `title` disappeares from `meta` in future due to some changes on the hoster's side the extraction would fail since `title` is mandatory. That's expected.
+If `title` disappears from `meta` in future due to some changes on the hoster's side the extraction would fail since `title` is mandatory. That's expected.
Assume that you have some another source you can extract `title` from, for example `og:title` HTML meta of a `webpage`. In this case you can provide a fallback scenario: