~mil/sxmo-devel

This thread contains a patchset. You're looking at the original emails, but you may wish to use the patch review UI. Review patch
1

[PATCH sxmo-docs] Fix spelling typos

Martin Vahlensieck
Details
Message ID
<20210528191607.48839-1-git@academicsolutions.ch>
DKIM signature
pass
Download raw message
Patch: +8 -8
---
 CONTRIBUTING.md |  2 +-
 SYSTEMGUIDE.md  |  4 ++--
 USERGUIDE.md    | 10 +++++-----
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f006e68..120b64d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -60,7 +60,7 @@ Also, you can check out the guide at: [https://git-send-email.io/](https://git-s


## **IRC Channel**
Our IRC channel for general adhoc development dicussion is:
Our IRC channel for general adhoc development discussion is:

- `#sxmo` on `irc.oftc.net`
- `#sxmo-offtopic` on `irc.oftc.net`
diff --git a/SYSTEMGUIDE.md b/SYSTEMGUIDE.md
index fcd703a..090f893 100644
--- a/SYSTEMGUIDE.md
+++ b/SYSTEMGUIDE.md
@@ -218,11 +218,11 @@ A variety of system activities trigger udev events which are matched by rules in

Notifications to the user are created by calling `/usr/bin/sxmo_notificationwrite.sh` with the appropriate arguments. These arguments are:
* The filepath of the notification to write (or "random" to generate a random id)
  * If "random" is specified, then the notification file will be created in `$NOTIFDIR` as specificed in `/usr/bin/sxmo_common.sh`.
  * If "random" is specified, then the notification file will be created in `$NOTIFDIR` as specified in `/usr/bin/sxmo_common.sh`.
* Action that the notification invokes upon selecting/tapping the notification window
  * select/tapping on the notification will trigger removal of the notification, as well as the associated action.
* The file to watch for deactivation (which occurs if anything at all happens to the file).
  * This file, if specified, should be one which will be affected by the user dealing with the interaction, in order to trigger removal of the notification. In the absence of a file, a string representing a non-existant file can be provided (e.g. "none")
  * This file, if specified, should be one which will be affected by the user dealing with the interaction, in order to trigger removal of the notification. In the absence of a file, a string representing a non-existent file can be provided (e.g. "none")
  * e.g. if a SMS text is removed, the watch file should be the one containing the SMS message, so when the user reads/deletes/saves the message, the notification will be removed.
* The text displayed in the notification

diff --git a/USERGUIDE.md b/USERGUIDE.md
index c794c16..857b286 100644
--- a/USERGUIDE.md
+++ b/USERGUIDE.md
@@ -44,7 +44,7 @@ layout that is activated (see [layouts](#stronglayoutsstrong)). The default layo
At the top-right you see the status menu, holding various symbols:

* The first icon indicates the state of the modem and the modem monitor:
    * A lock icon shows your modem's SIM is locked and needs to be unlocked with a PINj
    * A lock icon shows your modem's SIM is locked and needs to be unlocked with a PIN
    * A signal bar icon shows that you have a GSM connection
    * A cloud icon shows that you also have a data connection (2G/3G/4G)
* The wifi icon indicates you are connected to a wireless network
@@ -254,7 +254,7 @@ calls/texts. If your SIM is locked, you must unlock it manually.  The scripting

SXMO ask for your SIM's PIN code using dmenu (since sxmo 1.4.1).

Alterntively, you can do so from the command-line as follows:
Alternatively, you can do so from the command-line as follows:

```sh
mmcli -i 0 --pin 1234
@@ -340,7 +340,7 @@ Note that you should **always** prefix numbers you call out with, text to,
or add to the contact system **with their international prefix code**
and **with** the initial plus sign. Behind the scenes for `mmcli`, numbers always
come into the system with international prefixes from my testing. So if
you receieve a call from the number `54321` for example; it would come
you receive a call from the number `54321` for example; it would come
into mmcli as `+154321` if this was a US number. This means if you dial, text, and store contacts *with
the internationl prefix*, you can be assured that texts / outgoing /
incoming calls will line up in regards to deduplication of contacts in
@@ -554,7 +554,7 @@ Note: `$XDG_CACHE_HOME` by default is equal to `~/.cache`

### **Environment Variables**

The following enviroment variables can be set:
The following environment variables can be set:

<table>
  <tbody>
@@ -640,7 +640,7 @@ The following enviroment variables can be set:

### **User-customizable xinitrc**

For setting the above Enviroment Variables and also to launch custom
For setting the above Environment Variables and also to launch custom
programs upon starting X you can use the user customizable `xinit`
described in the Files and Folders section. You will automatically be
provided with a custom xinit based on the following template:
-- 
2.28.0
Details
Message ID
<87bl8uo62u.fsf@navi.i-did-not-set--mail-host-address--so-tickle-me>
In-Reply-To
<20210528191607.48839-1-git@academicsolutions.ch> (view parent)
DKIM signature
pass
Download raw message
Thanks! Merged:

To git.sr.ht:~mil/sxmo-docs
   7b0cf86..1be9a0b  master -> master
--
w:] www.momi.ca
pgp:] https://momi.ca/publickey.txt
Reply to thread Export thread (mbox)