Got a clue that feels flat-out wrong? Here's my go-to approach that usually gets editors to listen. First, note the essentials: puzzle title or publication, date, puzzle ID (if there is one), the exact clue text, the grid entry it produced, and the crossing letters. I always take a screenshot of the grid and the offending clue so there’s no ambiguity about which puzzle I mean. Then I check quick reference sources—dictionary definitions, style guides, or original-language sources if it’s a translation issue—to gather evidence.
Next I write a short, polite message. I lead with the exact puzzle details, paste the clue and fill, explain why it’s misleading or incorrect, and include links or quotes from references. If I can, I suggest an alternative clue or explain how the current clue violates a rule (ambiguity, incorrect facts, offensive language, etc.). I send this through the publication’s official feedback channel—website form, puzzle email, or the app’s feedback option—and I copy the constructor or post on their social account if that’s customary. Editors aren’t adversaries; they appreciate precise, civil reports. I usually sign off with a friendly line and a quick note that I enjoy the puzzles, which seems to help the message land. I’ve had a few rejections reversed this way, so it feels worth the effort.
One time I drafted a formal note that actually persuaded an editor to reinstate a clue I'd argued was valid, so here’s the form I favor. Lead with the metadata: publication name, puzzle author, publication date, and grid coordinates for the entry. Then paste the clue exactly, plus the fill. In the next paragraph, explain the problem succinctly—why the clue was deemed unacceptable and why that reasoning is incorrect or incomplete.
After that I include supporting evidence: dictionary citations, usage examples, links to archived sources, or citations from subject-matter references. If an alternative phrasing works better, I offer it. Keep the tone courteous; start with something like ‘I enjoy your puzzles’ and end with a brief sign-off. If the publisher has a ticketing system, use it; otherwise send an email or mention the constructor on social media without harassing them. Editors are human and appreciate thoughtful, referenced reports, and I still get a small thrill when a well-constructed note leads to a correction.
If a solver thinks a clue was wrongly rejected, I try to keep my critique crisp and evidence-based. Start by finding the publisher’s feedback route—many outlets have a ‘Contact the Puzzle Editor’ link or an in-app report function. If that’s missing, look for the constructor’s social media or an official email address linked to the puzzle page.
When I write, I include: the date and title, the clue verbatim, the grid letters, and the reason it’s bad (factually wrong, misleading grammar, unfair obscurity, or offensive content). I attach a screenshot and a source—dictionary entries, historical references, or language corpus examples—so the editor doesn’t have to chase facts. Being concise matters; long rants rarely help. If the publisher replies slowly, posting a civil thread on community boards or tagging the constructor can speed attention, but I avoid piling on or public shaming. Usually, clear evidence and a calm tone get the best responses, and sometimes I feel like I helped sharpen the puzzle for the next reader.
Quick checklist I use whenever I want a rejected clue re-evaluated: identify the exact puzzle (title/date), copy the clue and the grid entry, capture a screenshot, and gather supporting references (dictionary links, credible sources). Frame a short message explaining why the clue is wrong or unfair—state the error, cite proof, and propose a clearer alternative if you have one. Send this through the official feedback form or puzzle email; if that’s not available, a polite direct message to the constructor or a civil community post often works. Keep your tone calm and factual; editors respond much better to respectful, sourced notes. I usually close with a small compliment about the puzzle to keep it friendly, and that helps.
If you prefer a community route, I often use forums and social platforms to report rejected clues and spark constructive discussion. Post the puzzle details and the full clue, then lay out why it feels wrong—be specific about factual errors, grammatical issues, or cultural insensitivities. Attach screenshots and cite references so the thread doesn’t devolve into opinions. Tagging the constructor or the puzzle account can route the discussion to people who can actually change things.
On many sites a civil, evidence-backed thread draws helpful input from other solvers who may add historical context or alternate sources; that collective backing can persuade an editor faster than a lone message. I avoid piling on negativity: keep the tone collaborative, not accusatory. After a few such threads, I’ve noticed editors tend to engage more with posters who bring calm, well-documented points, and that feels really satisfying to be part of a solution.
2026-02-07 06:45:13
2
Ver Todas As Respostas
Escaneie o código para baixar o App
Livros Relacionados
Rejected
Ellie Scott
9.7
317.6K
"I reject you, Alpha! I reject you!".
Elizabeth is an Omega ranked wolf; however, she does not realize she is an Alpha by birth. She has been rejected by her family, and her Pack, having suffered years of abuse from them. She is about to be given to the Pack Beta as his chosen mate when her fated mate finds her. Will her fated mate reject her as well?
"GET THIS FAT, SHAPELESS COW OUT OF MY PRESENCE!"
I claimed our Alpha as my mate, he insulted and rejected me in front of the whole pack, resisting the mate bond.
"GET THIS FAT, SHAPELESS COW OUT OF MY PRESENCE!" He said, and even with his cruel words, my wolf whined and cried out to him.
Getting sold later for a few pennies was the worst heartbreak I could ever wish for. But not until I got a second chance at love with the Howling Alphas.
Being mated to 2 Alphas isn't a problem. But there are more and they're all fighting for my attention.
With war looming amongst the werewolf clan and plentiful revelations from the Moon Goddess, I'm presented as the solution to the ultimate problem, but that would mean even more pain for me.
Will my mates choose me over their pack and the entire werewolf clan, even though they have little or no choice in the matter?
Yet, with the ongoing chaos, someone is still staking his claim on me. Who is this man?
My name is Elle.
I am a beta female, but I live like an omega. Sometimes I don't even know what's better for me. I hoped that when I turned 18 my life would change. But everything got worse. At the age of 18, every werewolf knows his wolf. My wolf did not appear. In the last year I was simply wolfless. My mate rejected me and he is my the biggest nightmare.
But it is said that hope dies last, so until the last moment of my life I will believe that something good is prepared for me in this world as well.
Like I said, I'm Elle Parker. In the eyes of some, the most insignificant omega. But is that really the case?
QUICK PREVIEW
I would like to believe that this is possible. Moon Goddess ... can I get my rejection back? Please...
I take a deep breath, look up to the sky and hopefully say:
"I alpha Brandon Taylor take back my rejection and accept you Elle Parker as my mate, as my luna, as anythig you want to be in my life. I TAKE IT BACK!"
Then I fall to my knees crying. I feel a huge pain in my chest that seems to suffocate me, I lie down on the ground and close my eyes feeling how I slowly start to faint but not before hearing just like in a dream a warm and tender voice.
"I, Moon Goddess, accept your request!"
Maya is riding high after finally becoming a member of the pack. On that fateful night, the best and worst things happen to her. Not only does she turn into a wolf, but she finds her mate. None other than the pack’s nomad alpha, Luke. He doesn’t want her as his mate.
All he's ever needed was his bike and the freedom of the open road—until Maya. Luke knows he's made a mistake by rejecting Maya. Nothing else matters to him. Each time he visits the pack he hopes to see her, but she's perfected the art of avoiding him—until he decides to stay.
Maya wants to stay mad at Luke to protect herself, but with every passing day she learns more about their aloof alpha. She wants to give herself to him completely, but will she be risking more than her body?
He left once. He rejected her once. He’d been cruel. Is there any chance that he's really changed?
"You still think you’re the main character in your own story, don’t you, Mercer? That’s cute. You were written out the moment you let me inside you. You don’t exist without me now. And you love it."
Kade Mercer an unstoppable force on the ice, destined for the NHL. One reckless mistake, one desperate night, and it was all over. The trap was set long before he even stepped onto the ice. Nikolai Volkov, mafia kingpin and team owner, orchestrated it all—the seduction, the scandal, the blackmail. Now, Kade isn’t just owned. He’s trapped.
He still plays. He still wins. But only when they let him. Throw a game. Obey. Or lose everything.
But the real hell doesn’t come from Nikolai. It comes from his son, Rook Volkov. Golden boy of a rival team. Hockey’s rising star. Kade’s worst enemy. He’s spent years fighting Kade, hating him, wanting him. Now? He owns him.
Rook doesn’t destroy Kade’s career—he controls it. His flights. His bank accounts. His entire life. And when Kade resists? Rook makes him pay.
First, he makes him beg.
Then, he makes him like it.
Every punishment, every violation, every humiliating submission forces Kade deeper into the world Rook has carved out for him. A world where the line between rivalry and ownership has been erased. A world where Kade can fight all he wants—but he’ll never escape.
Because Rook isn’t keeping him prisoner.
Six years of marriage, and I'm finally pregnant!
My husband is an Alpha. To give him an heir, I had gone through countless rounds of ovulation shots, swallowed all sorts of herbal concoctions made by witch doctors, and even been forced to insert some strange things into my private parts!
But now, it's worked!
I planned a romantic road trip, hoping to surprise him when we got to the resort.
Of course, he insisted we bring Kelly along. Kelly is his Beta—beautiful, tough, and a bit of a warrior.
The heat was unbearable, so I went to the trunk to grab a soda from the small cooler, but Kelly accused me of trying to smash her with it.
"Apologize to Kelly!" my husband ordered firmly.
"No! I didn't do anything!" I protested.
So, they both dumped me in the middle of nowhere.
It took everything I had to escape the three Rogues who were after me. But when I finally made it back to the hotel, I found Kelly on top of my husband.
"Ana, you can't have children. Kelly just wanted to help us have one," he said shamelessly.