How to change the Windows shortcut you use for rewriting text
Change the default Win+Ctrl+R shortcut in Lightphrase Settings, then test the new combination on a short selection in an editable note. Check two things separately: whether the wheel opens and whether the chosen action completes. That distinction helps you avoid changing the shortcut to solve a problem with a particular text field.
Choose a combination you can use comfortably
Before changing the setting, consider the shortcuts you already use in Windows and your everyday applications. A combination can be awkward to hold, reserved by the system, or claimed by another program. Choose one you can press while making a deliberate wheel selection, rather than choosing solely because it is unusual.
Open Settings and change the rewrite shortcut. Check that the setting was accepted and that the displayed combination matches what you intended. If the app cannot register the combination or another program responds instead, choose a different one. The availability of a shortcut can depend on what else is running.
Keep a note of the previous setting while you test. Changing one combination at a time makes it easier to tell which choice you are using, especially if you switch between a laptop keyboard and an external keyboard.
Test that the wheel opens before testing a rewrite
Use a short, disposable note in an editable field. Select a sentence, then press and hold your new shortcut. Confirm that the wheel opens. Choose an action and complete the selection. If you release without choosing and the wheel remains open, select deliberately or cancel.
If no wheel appears, check the saved combination and whether another app is handling the keys. Test another available combination if needed. At this stage, the question is whether the shortcut can open the wheel; a rewrite’s wording is a separate question.
If the wheel opens, continue with the same note and choose Fix Grammar or Retone. Retone uses your selected tone unless Ask for tone is enabled in Settings → Tones, in which case you choose a saved tone at the tone step. Check the reported outcome and the text itself.
Use a short example to verify the chosen action
A useful test sentence has something specific to correct. Compare the output against the original rather than treating any change as success. These illustrative examples show the difference between tightening wording and correcting a grammatical error.
A new shortcut changes how you start the action, not what a correct rewrite should preserve. Names, dates, negations, ability, and promises still need to mean the same thing.
Before
Hi Dana, I wanted to reach out because I realize I never actually sent over the revised budget for the spring campaign. I can get it to you by Thursday, and I will also include the vendor comparison we discussed. Sorry for the delay.
After
Hi Dana, I realize I never sent the revised budget for the spring campaign. I can get it to you by Thursday, and I will include the vendor comparison we discussed. Sorry for the delay.
Before
Priya, the migration will move to the 14th because the staging environment were not ready. We will run the full test on the 12th and confirm before then. Nothing else change.
After
Priya, the migration will move to the 14th because the staging environment was not ready. We will run the full test on the 12th and confirm before then. Nothing else changes.
Separate a field limitation from a shortcut problem
The wheel can open correctly even when the target cannot accept a reliable replacement. Replacement actions normally edit the selection and restore the previous clipboard. If a result is copied instead, inspect it and paste it into an editable draft. A reported copy is a different outcome from the wheel failing to open.
If the test note works but your usual document does not, check the original field’s editing state and selection. A reading view or protected field may behave differently. Changing the shortcut does not make a read-only passage editable. If the action reports an error, address that outcome before trying to paste a result.
Retest in the applications you actually use
Once the note test works, try the shortcut in your usual editor, email draft, and chat draft with text you can safely edit. Confirm the wheel appears, select the intended action, and review the outcome in each field. One successful test does not establish compatibility with every control in an application.
If a conflict returns after another application starts, compare the same simple note again. Keep the shortcut that behaves consistently for your workflow, and record what happens when it fails: no wheel, no usable selection, a copied result, or an error. Those observations are more useful than repeatedly changing keys without testing one step at a time.
Take it into your next draft
Save a comfortable available shortcut, verify that it opens the wheel on a short editable note, and then test the action result. Retest in your everyday fields before relying on the new combination, keeping shortcut conflicts separate from selection and replacement limitations.