Celeb News

Emtee Apologizes to Mshini After Private Conversation Between the Two Went Viral

Emtee Apologizes to Mshini After Private Conversation Between the Two Went Viral. One thing about Emtee, he can trend for great music today, and the next day, something totally unrelated to his career, makes headlines. There is never a dull moment where he is concerned.

On Monday, the multi-award winning rapper made news after screenshots of DMs with other women made it to his Instagram stories. Some of the messages ranged from flirty to outright dissing. Many believe that those messages, have been leaked by Emtee’s wife, Nicole Kendall, who is also the mother of their three kids. The two have had a troubled marriage for years, with a history of taking their issues to social media.

One of the screenshots, was a conversation between Emtee and Mshini Lekwadu. From the message, the two personalities exchange greetings, and Emtee asked Mshini for her address, with the intention of visiting her. Mshini gave him the address, and stated she looked forward to their meeting that Friday. Social media users weighed in on the leaked conversation, and came up with a number of conclusion.

Seeing that her brand was getting tarnished, Mshini took to social media to clear her name. She explained that while on Big Brother, she openly supported Emtee due to his admiration for the artist’s music. Mshini emphasized that their subsequent DM exchanges were strictly professional. Meanwhile, Emtee was live on Instagram, revealing his romantic feelings for Mshini.

A day later, Emtee has come back to social media, this time with an apology. He started by appreciating Mshini for supporting her craft, while she was in Biggie’s house. Emtee then stated that he wanted to visit Mshini to personally thank her for her kindness. He also wanted to forge a professional work relationship with her, not anything romantic. Emtee concluded his statement by apologizing to Mshini and everyone concerned.

Related Articles

Back to top button

Adblock Detected

Please turn off your ad blocker first to read this article