Wednesday, 5 December 2012


Within moments of Kate Middleton’s announcement of her pregnancy with the Duke of Cambridge’s child, Prince Harry’s press secretary released a statement providing a detailed itinerary for the entirety of March 2012 as an alibi to dispel any rumours of his paternity in respect of the child, claiming: “the Prince was at least 100km from the Duchess of Cambridge at all times in the run-up to, during, and after her baby’s conception.”

In an additional pre-emptive move by the Prince's PR team, a list of former ginger-haired members of the House of Windsor was released to various newspapers, evidencing a long-established genealogically-ginger lineage, in order to quell, in advance, any press speculation in the event that the Duchess of Cambridge’s baby is born with ginger hair.

“We can’t take any chances,” said Verity Himmler-Rimmel, a close confidante of the Prince. “He wasn’t anywhere near the Duchess actually, the night of the conception he was attending a polysexual genocide-themed midget-throwing party in Cumbria. Still we want to quell any rumours before they start.”

The Sun claims to have information suggesting that Prince Harry may not have been in Cumbria for as long as his publicity team are suggesting.

“We paid a known stalker and rapist to hack some of the Prince’s friends’ phones, and fuck a duck, we found out some juicy stuff!” said a reporter (Glenn Dontcaire) who wished to remain anonymous. “After our hired criminal violently-violated the privacy and whatever else of a number of Harry’s friends, he discovered that Harry had left the midget-throwing party at ten o’clock that night, but he didn’t go home! Where did he go after that? Eh? Eh?”

There are rumours that The Sun are prepared to ‘bribe every single person in the country’ in order to find out; vowing to stop at nothing in the quest to dig-up enough puerile, derisive garbage to humiliate the Royal family and drive another princess to an assisted suicide.  

Prince Harry learns of the Duchess of Cambridge's pregnancy

No comments:

Post a Comment