update citation

paper.bib

@@ -1,11 +1,14 @@
-@Manual{rtweet,
-  title = {{r}tweet: Collecting {T}witter Data},
-  author = {Kearney, Michael W},
-  organization = {The {C}omprehensive {R} {A}rchive {N}etwork},
-  year = {2018},
-  note = {R package version 0.6.7},
-  url = {https://cran.r-project.org/package=rtweet},
-  doi = {10.5281/zenodo.2528481}
+@article{rtweet,
+  title = {rtweet: Collecting and analyzing Twitter data},
+    author = {Michael W. Kearney},
+    year = {2019},
+    note = {R package version 0.7.0},
+    journal = {Journal of Open Source Software},
+    volume = {4},
+    number = {42},
+    pages = {1829},
+    doi = {10.21105/joss.01829},
+    url = {https://joss.theoj.org/papers/10.21105/joss.01829}
 }
 
 @Manual{academictwitteR,

paper.md

@@ -38,7 +38,7 @@ Authorization for the Academic Research Product Track provides access to the Twi
 
 The ``academictwitteR`` package was designed: 1) to make the Academic Research Product Track easily accessible for R users by providing dedicated functions to query the the v2 API endpoints; 2) to encourage academic researchers efficiently and safely to store their data.
 
-The functions allow the user to collect tweets from (or to) specified users and to collect tweets containing specified words or sets of words. In particular, queries that include so-called "conjunction-required"" operators can also be accessed via a set of shortcut functions for accessing e.g. tweets containing media content, tweets containing geographic location information, or tweets containing urls. Additionally, separate query builder functions allow the user to specify complex queries to incorporate into the API call. 
+The functions allow the user to collect tweets from (or to) specified users and to collect tweets containing specified words or sets of words. In particular, queries that include so-called "conjunction-required" operators can also be accessed via a set of shortcut functions for accessing e.g. tweets containing media content, tweets containing geographic location information, or tweets containing urls. Additionally, separate query builder functions allow the user to specify complex queries to incorporate into the API call. 
 
 Data is stored in serialized form as RDS files or as separate JSON files. The former represents the most efficient storage solution for native R data-file formats; the latter helps mitigate loss by storing data as separate JSONs for each pagination token (or up to 500 tweets). Convenience functions are also included to bind tweet- and user-level information stored as JSON files, and to pick up data collection where it left off in the case of unplanned interruption.