delete trailing whitespace

README.md

@@ -85,8 +85,8 @@ By default, scarf-js will only trigger analytics when your package is installed
 #### As a user of a package using scarf-js, what information does scarf-js send about me?
 
 *Scarf does not store personally identifying information.* Scarf aims to collect information that is helpful for:
-- Package maintainence 
-- Identifying which companies are using a particular package, in order to set up support agreements between developers and companies. 
+- Package maintainence
+- Identifying which companies are using a particular package, in order to set up support agreements between developers and companies.
 
 Specifically, scarf-js sends:
 
@@ -143,7 +143,7 @@ Yes. By opting out of analytics via `package.json`, any package upstream will ha
 ```
 
 Installers of your packages will have scarf-js disabled for all dependencies upstream from yours.
-  
+
 
 ### Developing
 

WHY.org

@@ -21,7 +21,7 @@ What makes things even harder for these developers is, as Andrew Nesbitt puts it
 in this excellent [[https://www.youtube.com/watch?v=hW4wUpoBHr8][talk]]:
 
 #+BEGIN_QUOTE
-Maintainers are working mostly in the dark 
+Maintainers are working mostly in the dark
 #+END_QUOTE
 
 This is an important point. Package maintainers have little insight into how
@@ -43,7 +43,7 @@ statistics, as do npm and others. Unfortunately, the data they collect is
 still limited, and whether the data is even exposed to package maintainers
 directly varies between package managers.
 
-So what can we, the software development community do about this? 
+So what can we, the software development community do about this?
 
 One thing we could all do would be to convince our employers to support the
 awesome people that build and maintain the OSS they rely on. But you knew that