felixfoertsch/syncthing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Spelling fixes

Browse Source
This commit is contained in:
Alex Chan
2015-05-29 09:40:00 +01:00
parent 5aca789fea
commit f6b264275b
8 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/device-ids.rst
+1 -1
View File
@@ -117,7 +117,7 @@ possibilities here;
Once we have and address and port a TCP connection is established and a Once we have and address and port a TCP connection is established and a
TLS handshake performed. As part of the handshake both devices present TLS handshake performed. As part of the handshake both devices present
their certificates. Once the handshake has completed and the peer their certificates. Once the handshake has completed and the peer
certificiate is known, the following steps are performed. certificate is known, the following steps are performed.
1. Calculate the remote device ID by using the process above on the 1. Calculate the remote device ID by using the process above on the
received certificate. received certificate.
dev/release-schedule.rst
+1 -1
View File
@@ -25,7 +25,7 @@ downgrade to 0.7.x might be trickier.
Patch Releases Patch Releases
-------------- --------------
A new patch release is made each sunday, if there have been changes A new patch release is made each Sunday, if there have been changes
committed since the last release. Serious bugs, such as would crash the committed since the last release. Serious bugs, such as would crash the
client or corrupt data, cause an immediate (out of schedule) patch client or corrupt data, cause an immediate (out of schedule) patch
release. release.
dev/rest.rst
+1 -1
View File
@@ -2,7 +2,7 @@ REST API
======== ========
Syncthing exposes a REST interface over HTTP on the GUI port. This is Syncthing exposes a REST interface over HTTP on the GUI port. This is
used by the GUI code (Javascript) and can be used by other processes used by the GUI code (JavaScript) and can be used by other processes
wishing to control Syncthing. In most cases both the input and output wishing to control Syncthing. In most cases both the input and output
data is in JSON format. The interface is subject to change. data is in JSON format. The interface is subject to change.
events/itemfinished.rst
+2 -2
View File
@@ -2,7 +2,7 @@ ItemFinished
------------ ------------
Generated when Syncthing ends synchronizing a file to a newer version. A Generated when Syncthing ends synchronizing a file to a newer version. A
successfull operation: successful operation:
.. code:: json .. code:: json
@@ -19,7 +19,7 @@ successfull operation:
} }
} }
An unsuccessfull operation: An unsuccessful operation:
.. code:: json .. code:: json
intro/gui.rst
+1 -1
View File
@@ -19,7 +19,7 @@ A folder can be in any one of these states:
- *Stopped* when the folder has experienced an error, - *Stopped* when the folder has experienced an error,
- *Scanning* while the folder is lookign for local changes, - *Scanning* while the folder is looking for local changes,
- *Up to Date* when the folder is in sync with the rest of the cluster, - *Up to Date* when the folder is in sync with the rest of the cluster,
rest/db-status-get.rst
+1 -1
View File
@@ -16,7 +16,7 @@ Parameters: ``folder``, the ID of a folder.
"localBytes": 13173473780, "localBytes": 13173473780,
"localDeleted": 1847, "localDeleted": 1847,
"localFiles": 42106, "localFiles": 42106,
# which part of what we have locally is the latest cluster verision: # which part of what we have locally is the latest cluster version:
"inSyncBytes": 13173473780, "inSyncBytes": 13173473780,
"inSyncFiles": 42106, "inSyncFiles": 42106,
# which part of what we have locally should be fetched from the cluster: # which part of what we have locally should be fetched from the cluster:
users/autostart.rst
+3 -3
View File
@@ -184,7 +184,7 @@ How to use the system instance
Running Syncthing as a system service ensures that Syncthing is run at startup Running Syncthing as a system service ensures that Syncthing is run at startup
even if the Syncthing user has no active session. Since the system service even if the Syncthing user has no active session. Since the system service
keeps Syncthing running even without an active user session, it is inteded to keeps Syncthing running even without an active user session, it is intended to
be used on a *server*. be used on a *server*.
1. Create the user who should run the service, or choose an existing 1. Create the user who should run the service, or choose an existing
@@ -206,7 +206,7 @@ How to use the user instance
Running Syncthing as a user service ensures that Syncthing is run after the Running Syncthing as a user service ensures that Syncthing is run after the
Syncthing user has created a session (e.g. via the graphical login screen or Syncthing user has created a session (e.g. via the graphical login screen or
ssh). Thus, the user service is intended to be used on a *(multiuser) desktop ssh). Thus, the user service is intended to be used on a *(multiuser) desktop
computer*. It avoids unnecessarly running Syncthing instances. computer*. It avoids unnecessarily running Syncthing instances.
1. Create the user who should run the service, or choose an existing 1. Create the user who should run the service, or choose an existing
one. one.
@@ -233,7 +233,7 @@ subcommand:
Using the journal Using the journal
^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^
Systemd logs everything into the journal. You can easily acces Syncthing Systemd logs everything into the journal. You can easily access Syncthing
log messages (``-e`` lets the pager jump to the very end): log messages (``-e`` lets the pager jump to the very end):
:: ::
users/faq.rst
+2 -2
View File
@@ -246,9 +246,9 @@ also creates ``syncthing.log`` in Syncthing's home directory (check
How do I upgrade Syncthing? How do I upgrade Syncthing?
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
- If automatic upgrades is enabled (which is the default), Sycnthing will upgrade itself automatically within 24 hours of a new release. - If automatic upgrades is enabled (which is the default), Syncthing will upgrade itself automatically within 24 hours of a new release.
- The ugrade button appears in the web GUI when a new version has been released. Pressing it will perform an upgrade. - The upgrade button appears in the web GUI when a new version has been released. Pressing it will perform an upgrade.
- To force an upgrade from the command line, run ``syncthing -upgrade``. - To force an upgrade from the command line, run ``syncthing -upgrade``.