Talk:Korabl-Sputnik 3

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

Destruction edit

The Vostok programme article states the following: "After about 24 hours, the engines were intended to fire to begin reentry, but they fired for less time than had been expected. This meant that the spacecraft would enter the atmosphere, but not over Soviet territory. For this reason the self-destruct system was activated, so the spacecraft and the two dogs, were destroyed.[22] At the time the press reported that an incorrect attitude caused the cabin to be destroyed upon reentry.[22]" - Do what did really happen? There are citations for both versions. --StYxXx (talk) 09:11, 15 August 2012 (UTC)Reply

External links modified edit

Hello fellow Wikipedians,

I have just modified one external link on Korabl-Sputnik 3. 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) 10:43, 8 November 2017 (UTC)Reply