diff --git a/ReactNativeClient/lib/file-api-driver-webdav.js b/ReactNativeClient/lib/file-api-driver-webdav.js
index 0e16b14ce3..cec088d563 100644
--- a/ReactNativeClient/lib/file-api-driver-webdav.js
+++ b/ReactNativeClient/lib/file-api-driver-webdav.js
@@ -38,7 +38,7 @@ class FileApiDriverWebDav {
 	}
 
 	statFromResource_(resource, path) {
-		// WebDAV implementations are always slighly different from one server to another but, at the minimum,
+		// WebDAV implementations are always slightly different from one server to another but, at the minimum,
 		// a resource should have a propstat key - if not it's probably an error.
 		const propStat = this.api().arrayFromJson(resource, ['d:propstat']);
 		if (!Array.isArray(propStat)) throw new Error('Invalid WebDAV resource format: ' + JSON.stringify(resource));
diff --git a/ReactNativeClient/lib/layout-utils.js b/ReactNativeClient/lib/layout-utils.js
index 69727577eb..df7c97fbf3 100644
--- a/ReactNativeClient/lib/layout-utils.js
+++ b/ReactNativeClient/lib/layout-utils.js
@@ -1,9 +1,9 @@
 const layoutUtils = {};
 
-layoutUtils.size = function(prefered, min, max) {
-	if (prefered < min) return min;
-	if (typeof max !== 'undefined' && prefered > max) return max;
-	return prefered;
+layoutUtils.size = function(preferred, min, max) {
+	if (preferred < min) return min;
+	if (typeof max !== 'undefined' && preferred > max) return max;
+	return preferred;
 }
 
 module.exports = layoutUtils;
\ No newline at end of file
diff --git a/ReactNativeClient/lib/synchronizer.js b/ReactNativeClient/lib/synchronizer.js
index e0afc4d7c7..9f19c37e58 100644
--- a/ReactNativeClient/lib/synchronizer.js
+++ b/ReactNativeClient/lib/synchronizer.js
@@ -263,7 +263,7 @@ class Synchronizer {
 							//
 							// TODO: assuming a particular sync target is guaranteed to have accurate timestamps, the driver maybe
 							// could expose this with a accurateTimestamps() method that returns "true". In that case, the test
-							// could be done using the file timestamp and the potentially unecessary content loading could be skipped.
+							// could be done using the file timestamp and the potentially unnecessary content loading could be skipped.
 							// OneDrive does not appear to have accurate timestamps as lastModifiedDateTime would occasionally be
 							// a few seconds ahead of what it was set with setTimestamp()
 							remoteContent = await this.api().get(path);
@@ -567,7 +567,7 @@ class Synchronizer {
 					// If user has cancelled, don't record the new context (2) so that synchronisation
 					// can start again from the previous context (1) next time. It is ok if some items
 					// have been synced between (1) and (2) because the loop above will handle the same
-					// items being synced twice as an update. If the local and remote items are indentical
+					// items being synced twice as an update. If the local and remote items are identical
 					// the update will simply be skipped.
 					if (!hasCancelled) {
 						if (!listResult.hasMore) {