updated references to the renamed defaults button

data/key-mapper.glade

@@ -834,7 +834,7 @@
                         <property name="width-request">140</property>
                         <property name="visible">True</property>
                         <property name="can-focus">False</property>
-                        <property name="tooltip-text" translatable="yes">Click on a cell below and hit a key on your device. Click the "Apply Defaults" beforehand.</property>
+                        <property name="tooltip-text" translatable="yes">Click on a cell below and hit a key on your device. Click the "Restore Defaults" beforehand.</property>
                         <property name="margin-top">5</property>
                         <property name="margin-bottom">5</property>
                         <property name="label" translatable="yes">Key</property>

keymapper/gtk/window.py

@@ -293,7 +293,7 @@ class Window:
             # because the device is in grab mode by the daemon and
             # therefore the original keycode inaccessible
             logger.info('Cannot change keycodes while injecting')
-            self.show_status(CTX_ERROR, 'Use "Apply Defaults" before editing')
+            self.show_status(CTX_ERROR, 'Use "Restore Defaults" before editing')
 
     def get_focused_row(self):
         """Get the Row and its child that is currently in focus."""

readme/usage.md

@@ -17,7 +17,7 @@ row (as shown in the screenshots).
 For changes to take effect, save the preset first. Otherwise, the daemon
 won't be able to know about your changes. Afterwards press the "Apply" button.
 
-To change the mapping, you need to use the "Apply Defaults" button, so that
+To change the mapping, you need to use the "Restore Defaults" button, so that
 the application can read the original keycode. It would otherwise be
 invisible since the daemon maps it independently of the GUI.