diff --git a/NEWS b/NEWS
index 42fbac2..5cd5a2c 100644
--- a/NEWS
+++ b/NEWS
@@ -36,7 +36,7 @@ feedbackd 0.4.1
---------------
Released August 2024
* Simplify udev rule installation
-* Dont' fail tests with newer json-glib
+* Don't fail tests with newer json-glib
* Issues fixed:
* https://source.puri.sm/Librem5/feedbackd/-/issues/79
* Contributors:
@@ -50,7 +50,7 @@ Released June 2024
* Internal cleanups and restructuring to cater for different
LED types.
* Support RGB color mixing for multicolor leds
-* Allow to use (camera) flash LEDs as notificaton LED
+* Allow to use (camera) flash LEDs as notification LED
* Immediately end "too noisy" feedbacks when switching profile levels
* Issues fixed:
* https://source.puri.sm/Librem5/feedbackd/-/issues/77
diff --git a/README.md b/README.md
index f6fdf70..f7f031c 100644
--- a/README.md
+++ b/README.md
@@ -177,7 +177,7 @@ modified theme file in
If multiple theme files exist, the selection logic follows these steps:
1. It picks an identifier from the devicetree, until none are left
-1. It searches through the folders in `XDG_DATA_DIRS` in order of appearence,
+1. It searches through the folders in `XDG_DATA_DIRS` in order of appearance,
until none are left
1. If a theme file is found in the current location with the current name,
**it will be chosen** and other themes are ignored.
diff --git a/data/org.sigxcpu.feedbackd.gschema.xml b/data/org.sigxcpu.feedbackd.gschema.xml
index df76971..732726b 100644
--- a/data/org.sigxcpu.feedbackd.gschema.xml
+++ b/data/org.sigxcpu.feedbackd.gschema.xml
@@ -28,7 +28,7 @@
false
Prefer camera flash LED over notification LED
- Prefer the (camera) flash LED over other notifiction LEDs.
+ Prefer the (camera) flash LED over other notification LEDs.
diff --git a/debian/changelog b/debian/changelog
index 9c5ca24..67e39c1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -33,9 +33,9 @@ feedbackd (0.6.0) experimental; urgency=medium
[ Guido Günther ]
* event-naming-spec: Fix section description
- * event-naming-spec: Expand on notifiction events.
+ * event-naming-spec: Expand on notification events.
We move them to the system category as the notification server
- is a system component and add an event for now notifictions
+ is a system component and add an event for new notifications
for the notification server to use
* theme: Add notification-missed-new.
We'll remove message-new-notification somewhat later to not break
@@ -101,7 +101,7 @@ feedbackd (0.5.0) experimental; urgency=medium
[ Guido Günther ]
* packaging: Update lintian overrides
* packaging: Install NEWS and README. They contain useful information
- * packaging: Use pkgconf. It's prefered over pkg-config in Debian
+ * packaging: Use pkgconf. It's preferred over pkg-config in Debian
* doc: Document gsettings used by feedbackd
* udev: Add support for haptics on Oneplus Enchilada / Fajita.
The spmi_haptics driver isn't in mainline Linux as of Linux 6.11.
@@ -266,7 +266,7 @@ feedbackd (0.4.0) experimental; urgency=medium
even if the device is suspended.
* fbd-dev-led-qcom-multicolor: Support QCOM LPG LED multicolor.
QCOM LPG LEDs can also operate in a multicolor fashion.
- Re-use the probing sequence of multicolor LEDs and the hw_pattern
+ Reuse the probing sequence of multicolor LEDs and the hw_pattern
configuration of single color QCOM LPG LEDs.
* fbd-dev-leds: Probe QCOM HW LED types.
Try first the QCOM hardware LED types which require the most features of
@@ -486,7 +486,7 @@ feedbackd (0.0.2) experimental; urgency=medium
* Include specifications in the documentation.
Now that we can use markdown easily add them as they provide
help to the developer what events exist, etc.
- * dir-locals: Simlify consistent JS indenting
+ * dir-locals: Simplify consistent JS indenting
* feedback-vibra: Fix indentation
* tests: Test feedback theme name
* feedback-theme: No need for constructed.
@@ -700,13 +700,13 @@ feedbackd (0.0.0+git20210426) byzantium; urgency=medium
* event: Make log-domain match source file name
* tests: Run event tests too
* event: Remove 'g' prefix from common C types.
- This matchs phosh's style.
+ This matches phosh's style.
* fbd-event: Add sender property.
This allows us to store the DBus sender
* fbd-manager: Keep DBus sender around
* feedback-manager: Track DBus clients and end feedbacks if they go away.
When the client goes away we build up a list of events to end feedback
- for to make sure the hash table isn't modified in place. tThe alternative
+ for to make sure the hash table isn't modified in place. the alternative
approach would be to disconnect the on_event_feedbacks_ended handler,
duplicate the DBus signal emission and use g_hash_table_foreach_remove
but that looks less robust than using the same code path. (Closes: #25)
@@ -838,7 +838,7 @@ feedbackd (0.0.0+git20200714) amber-phone; urgency=medium
[ Guido Günther ]
* lfb-event: Clarify return values of `finished` functions.
- They just inidicate that we talked to feedbackd successfully.
+ They just indicate that we talked to feedbackd successfully.
* lfb-event: Connect done handler in async case too.
Otherwise the event state is not updated properly
* tests: Don't quit mainloop on event end.
@@ -886,7 +886,7 @@ feedbackd (0.0.0+git20200707) amber-phone; urgency=medium
trigger.
* data: Use LED feedback for missed calls, IMs and SMS
* Add generic missed notification.
- This can be used e.g. by the shell for general purpose notifictions
+ This can be used e.g. by the shell for general purpose notifications
but also for in app notifications of the foreground app.
* feedback-manager: Add hint to select feedback profile per event.
This e.g. allows events that are meant for haptic only to avoid
diff --git a/doc/feedback-themes.rst b/doc/feedback-themes.rst
index dea3682..7490847 100644
--- a/doc/feedback-themes.rst
+++ b/doc/feedback-themes.rst
@@ -51,7 +51,7 @@ The `Led` feedback type uses two properties to specify the way a LED blinks.
`green`, `blue` and `white` as well as values in the RGB HEX format (`#RRGGBB`) where
`RR`, `GG` and `BB` are two digit hex value between `00` and `FF` specifying the value of
each component. E.g. `#00FFFF` corresponds to cyan color.
-- `frequency`: The LEDs blinkinig frequencey in mHz.
+- `frequency`: The LEDs blinkinig frequency in mHz.
See also
========
diff --git a/doc/initialization.md b/doc/initialization.md
index a5d58c1..843de94 100644
--- a/doc/initialization.md
+++ b/doc/initialization.md
@@ -8,7 +8,7 @@ call [func@Lfb.init]() with the id of your application (usually
the desktop file name without the .desktop extension). For that you
include the `libfeedback.h` header. Since the API is considered
unstable at this point in time you need to acknowledge this by
-definining `LIBFEEDBACK_USE_UNSTABLE_API`:
+defining `LIBFEEDBACK_USE_UNSTABLE_API`:
```c
#define LIBFEEDBACK_USE_UNSTABLE_API
diff --git a/libfeedback/lfb-main.c b/libfeedback/lfb-main.c
index b317305..7059f9e 100644
--- a/libfeedback/lfb-main.c
+++ b/libfeedback/lfb-main.c
@@ -28,7 +28,7 @@ lfb_cancel_feedbacks (void)
while (g_hash_table_iter_next (&iter, &key, &value)) {
guint id = GPOINTER_TO_UINT(key);
g_hash_table_iter_remove (&iter);
- g_debug ("Cancellling feedback on shutdown %d", id);
+ g_debug ("Cancelling feedback on shutdown %d", id);
/* Need to use a sync call here since there might not be a main loop anymore */
lfb_gdbus_feedback_call_end_feedback_sync (_proxy, id, NULL, NULL);
}
diff --git a/src/fbd-dev-led-multicolor.c b/src/fbd-dev-led-multicolor.c
index e330155..287f200 100644
--- a/src/fbd-dev-led-multicolor.c
+++ b/src/fbd-dev-led-multicolor.c
@@ -79,7 +79,7 @@ fbd_dev_led_multicolor_probe (FbdDevLed *led, GError **error)
priv->blue_index = counter;
counter++;
} else {
- g_warning ("Unsupport LED color index: %d %s", counter, index[i]);
+ g_warning ("Unsupported LED color index: %d %s", counter, index[i]);
}
}
diff --git a/src/fbd-haptic-manager.c b/src/fbd-haptic-manager.c
index a886f35..d1fb3c3 100644
--- a/src/fbd-haptic-manager.c
+++ b/src/fbd-haptic-manager.c
@@ -133,7 +133,7 @@ fbd_feedback_manager_handle_vibrate (LfbGdbusFeedbackHaptic *object,
fbd_feedback_end (FBD_FEEDBACK_BASE (self->vibra));
if (fbd_dev_vibra_is_busy (vibra_dev)) {
g_debug ("Haptic busy");
- /* If there's an event with haptic deny haptic patter */
+ /* If there's an event with haptic deny haptic pattern */
lfb_gdbus_feedback_haptic_complete_vibrate (object, invocation, FALSE);
return TRUE;
}