From 2c9a940e1d847f74a8acc6d71e44a6d20ff804b4 Mon Sep 17 00:00:00 2001
From: Jeremy Banks <_@jeremy.ca>
Date: Mon, 31 Jan 2022 13:25:08 -0500
Subject: [PATCH] docs: correct "eyre::Error" to "eyre::Report" (#69)

---
 src/lib.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/lib.rs b/src/lib.rs
index 2868074..90fee4d 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -820,7 +820,7 @@ pub struct Chain<'a> {
 ///
 /// # const IGNORE: &str = stringify! {
 /// fn demo1() -> Result<T> {...}
-///            // ^ equivalent to std::result::Result<T, eyre::Error>
+///            // ^ equivalent to std::result::Result<T, eyre::Report>
 ///
 /// fn demo2() -> Result<T, OtherError> {...}
 ///            // ^ equivalent to std::result::Result<T, OtherError>
@@ -936,7 +936,7 @@ pub type Result<T, E = Report> = core::result::Result<T, E>;
 /// # Effect on downcasting
 ///
 /// After attaching a message of type `D` onto an error of type `E`, the resulting
-/// `eyre::Error` may be downcast to `D` **or** to `E`.
+/// `eyre::Report` may be downcast to `D` **or** to `E`.
 ///
 /// That is, in codebases that rely on downcasting, Eyre's wrap_err supports
 /// both of the following use cases: