added more information in the youtube-dl appendix

architecture design proposal.md

@@ -15,8 +15,8 @@ The following terms are used:
 
 ## Actor related
 
-- **Actors:** ActivityPub actors (https://www.w3.org/TR/activitypub/#actor-objects)
-- **Actor Types:** ActivityPub [Actor Types](https://www.w3.org/TR/activitystreams-vocabulary/#actor types)
+- **Actors:** ActivityPub [Actor Onbjects](https://www.w3.org/TR/activitypub/#actor-objects)
+- **Actor Types:** ActivityPub [Actor Types](https://www.w3.org/TR/activitystreams-vocabulary/#actor-types)
 - **WordPress actor types:** Things on WordPress that can be mapped to actors:
     - WordPress users
     - Whole site/blog (relay)
@@ -260,5 +260,5 @@ The registration of an actor type also registers every actor that is currently i
 
 ## The approach of youtube-dl
 
-[youtube-dl](https://github.com/ytdl-org/youtube-dl) is solving a similar problem with "extractors" that return data to the processing-chain of youtube-dl. They provide a base class that includes useful functions for common issues e.g. automatic testing, geo-bypassing, login/cookie/header management.
-They can also chain extractors recursivly, like a extractor for mastodon videos, that gets the video from the post and returns the source of the video, that could be youtube, vimeo or anything else youtube-dl supports.
+[youtube-dl](https://github.com/ytdl-org/youtube-dl) is solving a similar problem with "extractors" that return data to the processing-chain of youtube-dl. They provide a base class that includes useful functions for common issues e.g. automatic testing, geo-bypassing, login/cookie/header management. The most [basic extractor](https://github.com/ytdl-org/youtube-dl#adding-support-for-a-new-site) is about 40 lines of code.
+They can also chain extractors recursivly, like a extractor for mastodon videos, that gets the video from the post and returns the source of the video, that could be youtube, vimeo or anything else youtube-dl supports.