Fix wsgi touch

web/how_to_restrict_access_to_a_personal_homepage.markdown

@@ -71,7 +71,7 @@ Execute the following command on one of our managed Linux workstations:
 htpasswd -B -b -c ${HOME}/public_html/foo/.htpasswd bar foobar
 ```
 
-(You may also ommit the `-b` parameter and the password. Then you have to type it twice and blindly afterwards. The `-c` parameter is only needed the first time to create the `.htpasswd` file.)
+(You may also omit the `-b` parameter and the password. Then you have to type it twice and blindly afterwards. The `-c` parameter is only needed the first time to create the `.htpasswd` file.)
 
 
 Make sure, the `.htpasswd` and `.htaccess` files are world-readable, e.g. with:
@@ -88,7 +88,7 @@ otherwise the webserver won't have access to those files. Again, if you have you
 htpasswd -B -b ${HOME}/public_html/foo/.htpasswd fnord gna
 ```
 
-(You may also ommit the `-b` parameter and the password. Then you have to type it twice and blindly afterwards.)
+(You may also omit the `-b` parameter and the password. Then you have to type it twice and blindly afterwards.)
 
 See [Authentication and Authorization HowTo by Apache](https://httpd.apache.org/docs/2.4/howto/auth.html) for the gory details and further documentation.
 

web/wsgi.markdown

@@ -32,7 +32,7 @@ If you make changes to the source code, you have to tell the webserver to
 restart the WSGI app by modifying the file time stamp on the WSGI entry point:
 
 ```bash
-touch /home/wwwshare/public/wwwshare.wsgi
+touch /home/<wwwshare>/public/<wwwshare>.wsgi
 ```
 
 Note: [[SSH access|/web/webshares/#ssh-access]] is recommended for developers.