message: only use single ticks for find_package documentation
diff: @@ -162,14 +162,14 @@ example applications use
  Finding OSPRay with CMake
  =========================
  -Client applications using OSPRay can find it with CMake's ```find_package()```
  +Client applications using OSPRay can find it with CMake's `find_package()`
  command. For example:
  find_package(ospray 1.8.0 REQUIRED)
  -finds OSPRay according to where ```ospray_DIR``` points to OSPRay's config file:
  -```osprayConfig.cmake```. This file can be found in\
  -`${install_location}/[lib|lib64]/cmake`, where ```ospray_DIR``` can be specified
  +finds OSPRay according to where `ospray_DIR` points to OSPRay's config file:
  +`osprayConfig.cmake`. This file can be found in\
  +`${install_location}/[lib|lib64]/cmake`, where `ospray_DIR` can be specified
  as either an environment variable or CMake variable in the client CMake
  build. Once OSPRay is found, the following is all that is required to use
  OSPRay:
  @@ -182,9 +182,9 @@ library).
  Advanced users may want to link to additional targets which are exported in
  OSPRay's CMake config, which includes all installed modules. All targets
  -built with OSPRay are exported in the ```ospray::``` namespace, therefore all
  +built with OSPRay are exported in the `ospray::` namespace, therefore all
  targets locally used in the OSPRay source tree can be accessed from an
  -install. For example, ```ospray_common``` can be consumed directly via the
  -```ospray::ospray_common``` target. All targets have their libraries,
  +install. For example, `ospray_common` can be consumed directly via the
  +`ospray::ospray_common` target. All targets have their libraries,
  includes, and definitions attached to them for public consumption (please
  report bugs if one is found!).
  