Talk:William Catesby

Latest comment: 6 years ago by InternetArchiveBot in topic External links modified

Confusion of this William Catesby with his father edit

I noticed a problem when 1408 was presented as the birth year of this Catesby. This would have made him 65 when Richard III ascended the English throne. To my knowledge Richard III's Catesby was Richard's contemporary, and the Wars of the Roses website bears this out. 1408 may have been the birth year for the father of Richard III's counselor, who was also named William Catesby. Richard III's William Catesby inherited his father William's estates, so the estates attributed to him in the lead sentence are accurate.--Drboisclair (talk) 14:11, 11 April 2011 (UTC)Reply

External links modified edit

Hello fellow Wikipedians,

I have just modified one external link on William Catesby. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 14:51, 9 December 2017 (UTC)Reply