diff --git a/page-appform.php b/page-appform.php
index 71762d9e4..8dd680d79 100644
--- a/page-appform.php
+++ b/page-appform.php
@@ -19,7 +19,7 @@
Link to your app on the appstore
Link to the public repository
-
+
Fellow authors
Why is the app ready for users
@@ -28,4 +28,4 @@
--->
\ No newline at end of file
+-->
diff --git a/page-connect.php b/page-connect.php
index 5aaddfa5f..a396b4b90 100644
--- a/page-connect.php
+++ b/page-connect.php
@@ -34,7 +34,7 @@
How about security?
All of the security associated with Nextcloud is at work when you use the Nextcloud Proxy service. Nextcloud is still run by you, on your computer. You can monitor what is happening, manage accounts, check the logs, use your own SSL certificates, enable automatic updates and more. The appliance pre-configures much of Nextcloud for you. All you have to do is start the appliance, complete the setup and log into the web URL it provides. The Nextcloud browser wizard at the provided URL will step you through logging in for the first time. Of course, as you configure accounts for others to share on your Nextcloud, we recommend you use secure and complex passwords for all accounts.
-
However, we want to be completely transparent about the nature of Nextcloud Proxy. The Nextcloud Proxy app is distributed and the source code is in the Nextcloud repository for review in Github. The Nextcloud Proxy service is provided by PageKite. All files transferred through the Nextcloud Proxy service do pass through its data centers, and for a brief time are readable as the Nextcloud Proxy service transfers incoming requests from SSL to a pageKite protocol on the way to the private Nextcloud Server. In theory, if someone wanted to, all files transferred to and from devices using the Nextcloud Proxy service could – for that brief instant of time that they are being moved from the SSL terminated connection to the tunnel in memory – be read by someone with Nextcloud Proxy service server access. While the risk is small, and our terms and conditions cover this situation, it is something we wanted to be clear about. However, there is no way for the Nextcloud Proxy service to access your data on your private server, it can only broker a connection with your private server.
+
However, we want to be completely transparent about the nature of Nextcloud Proxy. The Nextcloud Proxy app is distributed and the source code is in the Nextcloud repository for review in GitHub. The Nextcloud Proxy service is provided by PageKite. All files transferred through the Nextcloud Proxy service do pass through its data centers, and for a brief time are readable as the Nextcloud Proxy service transfers incoming requests from SSL to a pageKite protocol on the way to the private Nextcloud Server. In theory, if someone wanted to, all files transferred to and from devices using the Nextcloud Proxy service could – for that brief instant of time that they are being moved from the SSL terminated connection to the tunnel in memory – be read by someone with Nextcloud Proxy service server access. While the risk is small, and our terms and conditions cover this situation, it is something we wanted to be clear about. However, there is no way for the Nextcloud Proxy service to access your data on your private server, it can only broker a connection with your private server.
How are Nextcloud Proxy and the Nextcloud Server Appliance different than Nextcloud?
diff --git a/page-contribute.php b/page-contribute.php
index 305ce99c5..cfcfa429b 100644
--- a/page-contribute.php
+++ b/page-contribute.php
@@ -57,7 +57,7 @@
Translate Nextcloud to your language. Go to Transifex and get going!
Help us improve the Nextcloud documentation! Find out how to make a difference in this contribution guide !
-
The animation shows the easiest way to contribute to the Nextcloud documentation. Go to the documentation in Github , click the
+
The animation shows the easiest way to contribute to the Nextcloud documentation. Go to the documentation in GitHub , click the
'edit' icon on a page, make the changes and create a pull request. This will notify the documentation maintainers of your proposed change and after review, it can be included!
-->
testing, grab a daily build. Our Github project is here and the issue tracker for the server here .
+ If you want to help out with developing and testing, grab a daily build. Our GitHub project is here and the issue tracker for the server here .
Daily build
Latest testing version:
diff --git a/page-webrtc.php b/page-webrtc.php
index f6178ed63..5ce8b34da 100644
--- a/page-webrtc.php
+++ b/page-webrtc.php
@@ -126,7 +126,7 @@
You should now have Spreed WebRTC installed.
2. Install the Spreed.ME Nextcloud app
- We'll now install the Spreed.ME app. This can be done either from the Nextcloud App Store (if it is available there for your version of Nextcloud) or, as we'll show here, directly from Github.
+
We'll now install the Spreed.ME app. This can be done either from the Nextcloud App Store (if it is available there for your version of Nextcloud) or, as we'll show here, directly from GitHub.
cd /srv/www/htdocs/nextcloud/apps
Go to the Nextcloud app folder on your server