wrap biocViews in backticks

Author: LiNk-NY

description-file.Rmd

@@ -192,7 +192,7 @@ package type (i.e., `Software`, `AnnotationData`, `ExperimentData`, or
 `Workflow`). `biocViews` terms are case-sensitive.
 
 The field name "biocViews" is case-sensitive and must begin with a lower-case
-'b'. Please use a single line with biocViews separated by commas
+'b'. Please use a single line with `biocViews` separated by commas
 
 (i.e,`biocViews: GeneTarget, SingleCell`).
 

important-bioc-features.Rmd

@@ -6,7 +6,7 @@ Packages added to the _Bioconductor_ Project require a `biocViews:`
 field in their `DESCRIPTION` file.  The field name "biocViews" is
 case-sensitive and must begin with a lower-case 'b'.
 
-biocViews terms are "keywords" used to describe a given package. They
+`biocViews` terms are "keywords" used to describe a given package. They
 are broadly divided into four categories, representing the type of
 packages present in the _Bioconductor_ Project 
 
@@ -15,29 +15,29 @@ packages present in the _Bioconductor_ Project
 3. Experiment Data
 4. Workflow
 
-biocViews are available for the [release][release-biocviews] and [devel][biocViews] branches of
-_Bioconductor_. The devel branch has a check box under the tree
-structure which, when checked, displays biocViews that are defined but
-not used by any package, in addition to biocViews that are in use. See also
-[description section](#description-biocviews)
+`biocViews` are available for the [release][release-biocviews] and
+[devel][biocViews] branches of _Bioconductor_. The devel branch has a check box
+under the tree structure which, when checked, displays `biocViews` that are
+defined but not used by any package, in addition to `biocViews` that are in use.
+See also [description section](#description-biocviews)
 
 ### Motivation {#biocviews-motivation}
 
-One can use biocViews for two broad purposes.
+One can use `biocViews` for two broad purposes.
 
 1. A researcher might want to identify all packages in the
    _Bioconductor_ Project which are related to a specific purpose.
    For example, one may want to look for all packages related to "Copy
    Number Variants".
 
 2. During development, a package contributor can "tag" their package
-   with biocViews so that when someone looking for packages (like in
+   with `biocViews` so that when someone looking for packages (like in
    scenario 1) can easily find their package.
 
 ### biocViews during new package development {#biocviews-pkg-devel}
 
 Visit the ['devel' biocViews][biocViews] when you are in the process of
-adding biocViews to your new package. Identify as many terms as
+adding `biocViews` to your new package. Identify as many terms as
 appropriate from the hierarchy. Prefer 'leaf' terms at the end of the
 hierarchy, over more inclusive terms. Remember to check the box
 displaying all available terms.
@@ -46,30 +46,30 @@ Please Note:
 
 1. Your package will belong to only one part of _Bioconductor_ Project
    (Software, Annotation Data, Experiment Data, Workflow), so choose only
-   biocViews from that category.
+   `biocViews` from that category.
 
-2. biocViews listed in your package must match exactly (e.g.,
-   spelling, capitalization) the terms in the biocViews hierarchy.
+2. `biocViews` listed in your package must match exactly (e.g.,
+   spelling, capitalization) the terms in the `biocViews` hierarchy.
 
 When you submit your new package for review , your package is checked
 and built by the _Bioconductor_ Project.  We check the following for
 biocViews:
 
-1. Package contributor has added biocViews.
+1. Package contributor has added `biocViews`.
 
-2. biocViews are valid.
+2. `biocViews` are valid.
 
-3. Package contributor has added biocViews from only one of the categories.
+3. Package contributor has added `biocViews` from only one of the categories.
 
-If you receive a "RECOMMENDED" direction for any of these biocViews
+If you receive a "RECOMMENDED" direction for any of these `biocViews`
 after you have submitted your package, you can try correcting them on
 your own following the directions given here or ask your package
 reviewer for more information.
 
-If a developer thinks a biocViews term should be added to the current acceptable
-list, please email [email protected] requesting the new biocView, under
-which hierarchy the term should be placed, and the justification for the new
-term.
+If a developer thinks a `biocViews` term should be added to the current
+acceptable list, please email <[email protected]> requesting the new
+`biocViews` term, under which hierarchy the term should be placed, and the
+justification for the new term.
 
 
 ## Common Bioconductor Methods and Classes {#reusebioc}