Fix documentation issues

The try.xts() example was more than 100 characters wide, which threw a
warning in R CMD check.

The [timeSeries] link was malformed because it was missing the second
component with package reference.

R/reclass.R

@@ -114,7 +114,7 @@ use.xts <- try.xts
 #' try.xts(a, error = FALSE)  # fails silently, still an integer vector
 #' 
 #' # control the result with a function
-#' try.xts(a, error = function(x, ...) { paste0("I'm sorry ", Sys.info()[["user"]], ", I'm afraid I can't do that.") })
+#' try.xts(a, error = function(x, ...) { "I'm afraid I can't do that." })
 #' 
 #' z <- zoo(1:10, timeBasedSeq("2020-01-01/2020-01-10"))
 #'

R/xts.R

@@ -412,8 +412,9 @@ function(x) {
 #' format for use within \R.
 #' 
 #' `as.xts()` can convert objects of the following classes into an xts object:
-#' object: [timeSeries], [ts], [matrix], [data.frame], and [zoo]. `xtsible()`
-#' safely checks whether an object can be converted to an xts object.
+#' object: [timeSeries][timeSeries::timeSeries], [ts], [matrix], [data.frame],
+#' and [zoo]. `xtsible()` safely checks whether an object can be converted to
+#' an xts object.
 #' 
 #' Additional `name = value` pairs may be passed to the function to be added to
 #' the new object. A special [`print.xts()`] method ensures the attributes are