minor cleanings

.Rbuildignore

@@ -3,12 +3,8 @@
 ^data-src$
 ^examples$
 ^README\.Rmd$
-^docs$
 ^cran-comments\.md$
 ^revdep$
 ^_pkgdown\.yml$
-^CONDUCT\.md$
-^CONTRIBUTING\.md$
-^ISSUE_TEMPLATE\.md$
 ^inst/vtests\.Rmd$
 ^\.github$

README.Rmd

@@ -18,8 +18,10 @@ knitr::opts_chunk$set(
 ![cranlogs](https://cranlogs.r-pkg.org/badges/mschart)
 ![Active](http://www.repostatus.org/badges/latest/active.svg)
 
-The `mschart` package provides a framework for easily create charts for 'Microsoft PowerPoint' documents. It has to be used with package [`officer`](https://davidgohel.github.io/officer) that will produce 
-the charts in new or existing PowerPoint or Word documents.
+The `mschart` package provides a framework for easily create charts for
+'Microsoft PowerPoint' documents. It has to be used with package
+[`officer`](https://davidgohel.github.io/officer) that will produce the charts
+in new or existing PowerPoint or Word documents.
 
 ![](https://www.ardata.fr/img/illustrations/ms_barchart.png)
 
@@ -52,7 +54,9 @@ doc <- ph_with(doc, value = linec, location = ph_location_type(type = "body"))
 print(doc, target = "example.pptx")
 ```
 
-At any moment, you can type `print(your_chart, preview = TRUE)` to preview the chart in a temporary PowerPoint file. This requires to have a PowerPoint Viewer installed on the machine.
+At any moment, you can type `print(your_chart, preview = TRUE)` to preview the
+chart in a temporary PowerPoint file. This requires to have a PowerPoint Viewer
+installed on the machine.
 
 ## Installation
 
@@ -71,23 +75,24 @@ install.packages("mschart")
 
 ## Contributing to the package
 
-### Code of Conduct
-
-Anyone getting involved in this package agrees to our [Code of Conduct](https://github.com/ardata-fr/mschart/blob/master/CONDUCT.md).
-
 ### Bug reports
 
-When you file a [bug report](https://github.com/ardata-fr/mschart/issues), please spend some time making it easy for me to follow and reproduce. The more time you spend on making the bug report coherent, the more time I can dedicate to investigate the bug as opposed to the bug report.
+When you file a [bug report](https://github.com/ardata-fr/mschart/issues),
+please spend some time making it easy for me to follow and reproduce. The more
+time you spend on making the bug report coherent, the more time I can dedicate
+to investigate the bug as opposed to the bug report.
 
 ### Contributing to the package development
 
 A great way to start is to contribute an example or improve the documentation.
 
-If you want to submit a Pull Request to integrate functions of yours, please provide:
+If you want to submit a Pull Request to integrate functions of yours, please
+provide:
 
 * the new function(s) with code and roxygen tags (with examples)
 * a new section in the appropriate vignette that describes how to use the new function
 * add corresponding tests in directory `tests/testthat`.
 
 By using rhub (run `rhub::check_for_cran()`), you will see if everything is ok.
-When submitted, the PR will be evaluated automatically on travis and appveyor and you will be able to see if something broke.
+When submitted, the PR will be evaluated automatically on travis and appveyor
+and you will be able to see if something broke.

README.md

@@ -65,11 +65,6 @@ install.packages("mschart")
 
 ## Contributing to the package
 
-### Code of Conduct
-
-Anyone getting involved in this package agrees to our [Code of
-Conduct](https://github.com/ardata-fr/mschart/blob/master/CONDUCT.md).
-
 ### Bug reports
 
 When you file a [bug