forked from MapComplete/MapComplete
		
	Fix a few typos in the README
This commit is contained in:
		
							parent
							
								
									78acb2794e
								
							
						
					
					
						commit
						14e8606ad6
					
				
					 1 changed files with 3 additions and 3 deletions
				
			
		| 
						 | 
					@ -60,7 +60,7 @@ A typical user journey would be:
 | 
				
			||||||
    * Note that _all messages_ must be read before being able to add a point.
 | 
					    * Note that _all messages_ must be read before being able to add a point.
 | 
				
			||||||
    * In other words, sending a message to a misbehaving MapComplete user acts as having a **zero-day-block**. This is added deliberately to make sure new users _have_ to read feedback from the community.
 | 
					    * In other words, sending a message to a misbehaving MapComplete user acts as having a **zero-day-block**. This is added deliberately to make sure new users _have_ to read feedback from the community.
 | 
				
			||||||
    
 | 
					    
 | 
				
			||||||
4. At 50 changesets, the [personal layout](https://pietervdvn.github.io/MapComplete/personal.html) is advertised. The personal theme is a theme where contributors can pick layers from all the offical themes. Note that the personal theme is always available.
 | 
					4. At 50 changesets, the [personal layout](https://pietervdvn.github.io/MapComplete/personal.html) is advertised. The personal theme is a theme where contributors can pick layers from all the official themes. Note that the personal theme is always available.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
5. At 200 changesets, the tags become visible when answering questions and when adding a new point from a preset. This is to give more control to power users and to teach new users the tagging scheme
 | 
					5. At 200 changesets, the tags become visible when answering questions and when adding a new point from a preset. This is to give more control to power users and to teach new users the tagging scheme
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					@ -131,7 +131,7 @@ Images are fetched from:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Images are uploaded to Imgur, as their API was way easier to handle. The URL is written into the changes.
 | 
					Images are uploaded to Imgur, as their API was way easier to handle. The URL is written into the changes.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
The idea is that once in a while, the images are transfered to wikipedia or that we hook up wikimedia directly (but I need some help in getting their API working).
 | 
					The idea is that once in a while, the images are transferred to wikipedia or that we hook up wikimedia directly (but I need some help in getting their API working).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Uploading changes
 | 
					### Uploading changes
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					@ -149,7 +149,7 @@ All documentation can be found in [here](Docs/)
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Privacy is important, we try to leak as little information as possible.
 | 
					Privacy is important, we try to leak as little information as possible.
 | 
				
			||||||
All major personal information is handled by OSM.
 | 
					All major personal information is handled by OSM.
 | 
				
			||||||
Geolocation is available on mobile only throught hte device's GPS location (so no geolocation is sent of to Google).
 | 
					Geolocation is available on mobile only through the device's GPS location (so no geolocation is sent of to Google).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
TODO: erase cookies of third party websites and API's
 | 
					TODO: erase cookies of third party websites and API's
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue