version 1.3.0

Introduce the `rich_text` feature and uses its own API credentials (see Issue #28).

- Rich Text. Upload rich documents to Google Docs where important text that should not be changed is automatically highlighted.
- API Credentials. Now, trackdown uses its own Goole API credentials (OAuth client ID and secret).

Author: ClaudioZandonella

DESCRIPTION

@@ -1,6 +1,6 @@
 Package: trackdown
 Title: Collaborative Editing of Rmd (or Rnw) Documents in Google Drive
-Version: 1.2.1
+Version: 1.3.0
 Authors@R:
     c(person(given = "Emily",
              family = "Kothe",

NEWS.md

@@ -1,5 +1,12 @@
 # trackdown (development version)
 
+## trackdown 1.3.0
+
+Introduce the `rich_text` feature and uses its own API credentials (see Issue #28)
+
+- **`rich_text`.** Upload *rich* documents to Google Docs where important text that should not be changed is automatically highlighted (e.g., placeholders hiding the code, header of the document, code chunks, and in-line code). See [rich-text feature details]( https://claudiozandonella.github.io/trackdown/articles/trackdown-features.html#rich-text).
+- **API Credentials.** Now, `trackdown` uses its own Goole API credentials (OAuth client ID and secret). See details on privacy policy at `vignette("trackdown-privacy-policy")` and [issue comment](https://github.com/ClaudioZandonella/trackdown/issues/28#issuecomment-1057195007).
+
 ## trackdown 1.2.1
 
 Corrige output message pull request #29 (by @chainsawriot)

README.Rmd

@@ -32,10 +32,10 @@ knitr::opts_chunk$set(
 
 The `trackdown` package offers a simple solution for collaborative writing and editing of R Markdown (or Sweave) documents. Using `trackdown`, the local `.Rmd` (or `.Rnw`) file can be uploaded as a plain-text file to Google Drive. By taking advantage of the easily readable Markdown (or LaTeX) syntax and the well-known online interface offered by Google Docs, collaborators can easily contribute to the writing and editing process. After integrating all authors’ contributions, the final document can be downloaded and rendered locally.
 
-> From `trackdown` v1.3.0 [currently only available on GitHub], the `trackdown` package introduces the `rich_text` feature and uses its own API credentials .
+> From `trackdown` v1.3.0 [currently only available on GitHub], the `trackdown` package introduces the `rich_text` feature and uses its own API credentials.
 > 
 > - **`rich_text`.** Upload *rich* documents to Google Docs where important text that should not be changed is automatically highlighted (e.g., placeholders hiding the code, header of the document, code chunks, and in-line code). This prevents collaborators from inadvertently making changes to the code which might corrupt the file. See [rich-text feature details]( https://claudiozandonella.github.io/trackdown/articles/trackdown-features.html#rich-text).
-> - **API Credentials.** Now, `trackdown` uses its own Goole API credentials (OAuth client ID and secret). This requires authentication to enable *“Trackdown R Package”*. The project is undergoing Google verification so it is already available but Google displays a worning message (see details at [issue comment](https://github.com/ClaudioZandonella/trackdown/issues/28#issuecomment-1057195007)). Don't worry `trackdown` uses the same system as `googledirve` package that was previously used. See details on privacy policy at `vignette("trackdown-privacy-policy")`).
+> - **API Credentials.** Now, `trackdown` uses its own Goole API credentials (OAuth client ID and secret). This requires google authentication and to enable *“Trackdown R Package”*. The project is undergoing Google verification so it is already available but Google displays a worning message (see details at [issue comment](https://github.com/ClaudioZandonella/trackdown/issues/28#issuecomment-1057195007)). Don't worry `trackdown` uses the same system as `googledirve` package that was previously used. See details on privacy policy at `vignette("trackdown-privacy-policy")`).
 
 ## Installation {#install}
 

README.md

@@ -28,7 +28,7 @@ locally.
 
 > From `trackdown` v1.3.0 \[currently only available on GitHub\], the
 > `trackdown` package introduces the `rich_text` feature and uses its
-> own API credentials .
+> own API credentials.
 >
 > -   **`rich_text`.** Upload *rich* documents to Google Docs where
 >     important text that should not be changed is automatically
@@ -38,9 +38,9 @@ locally.
 >     might corrupt the file. See [rich-text feature
 >     details](https://claudiozandonella.github.io/trackdown/articles/trackdown-features.html#rich-text).
 > -   **API Credentials.** Now, `trackdown` uses its own Goole API
->     credentials (OAuth client ID and secret). This requires
->     authentication to enable *“Trackdown R Package”*. The project is
->     undergoing Google verification so it is already available but
+>     credentials (OAuth client ID and secret). This requires google
+>     authentication and to enable *“Trackdown R Package”*. The project
+>     is undergoing Google verification so it is already available but
 >     Google displays a worning message (see details at [issue
 >     comment](https://github.com/ClaudioZandonella/trackdown/issues/28#issuecomment-1057195007)).
 >     Don’t worry `trackdown` uses the same system as `googledirve`