[VecOps][NFC] Don't use the name TVec in the comments but rather RVec

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());

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)