diff --git a/tutorials/vecops/vo001_AdoptOrOwnMemory.C b/tutorials/vecops/vo001_AdoptOrOwnMemory.C
index 18f5a51c944ffaff023911b5df4963853320ce34..9e8370a0e6cc4be98bc3b446cb02b165bf49ebd0 100644
--- a/tutorials/vecops/vo001_AdoptOrOwnMemory.C
+++ b/tutorials/vecops/vo001_AdoptOrOwnMemory.C
@@ -37,7 +37,7 @@ void vo001_AdoptOrOwnMemory()
 
    // Now, upon reallocation, the RVec stops adopting the memory and starts owning it. And yes,
    // a copy is triggered. Indeed internally the storage of the RVec is an std::vector. Moreover,
-   // the interface of the TVec is very, very similar to the one of std::vector: you have already
+   // the interface of the RVec is very, very similar to the one of std::vector: you have already
    // noticed it when the `data()` method was invoked, right?
 
    v2.push_back(UponCopyPrinter());
diff --git a/tutorials/vecops/vo001_AdoptOrOwnMemory.py b/tutorials/vecops/vo001_AdoptOrOwnMemory.py
index e48085e967fed6fccf310f4d3c265ff098b3e48b..cfdb250f4698e91939080e1da6de54d4b8b115ee 100644
--- a/tutorials/vecops/vo001_AdoptOrOwnMemory.py
+++ b/tutorials/vecops/vo001_AdoptOrOwnMemory.py
@@ -39,7 +39,7 @@ print("%s and %s" %(v.data(), v2.data()))
 
 # Now, upon reallocation, the RVec stops adopting the memory and starts owning it. And yes,
 # a copy is triggered. Indeed internally the storage of the RVec is an std::vector. Moreover,
-# the interface of the TVec is very, very similar to the one of std::vector: you have already
+# the interface of the RVec is very, very similar to the one of std::vector: you have already
 # noticed it when the `data()` method was invoked, right?
 v2.resize(4)