docs: align rendering wording with house style

Minor wording polish in the Overview and Pose convention sections — renderer naming aligned with internal house style. No methodology, data, or disclosure changes; downloads unaffected.

README.md

@@ -34,7 +34,7 @@ Synthetic training data for robotic bin picking — RGB, depth, instance masks,
 
 ## Overview
 
-Generated via physically-based ray tracing in Blender Cycles, this dataset delivers dense, photorealistic scenes of cluttered bins at warehouse scale. Each scene includes RGB, 32-bit depth, instance segmentation, camera intrinsics/extrinsics, and per-instance 6D pose with visibility ratios.
+Generated via physically-based ray tracing with Cycles, this dataset delivers dense, photorealistic scenes of cluttered bins at warehouse scale. Each scene includes RGB, 32-bit depth, instance segmentation, camera intrinsics/extrinsics, and per-instance 6D pose with visibility ratios.
 
 The dataset's value is simple: synthetic renders give perfect ground truth annotations impossible to obtain from real cameras, at a scale and cost real-world collection cannot match. Use it to train 6D pose estimators, bin-picking grasp predictors, and warehouse perception systems — then validate sim-to-real transfer on smaller real-world test sets.
 
@@ -154,7 +154,7 @@ Training 6D pose estimation models, bin-picking grasp models, and warehouse robo
 
 ## Pose convention
 
-This release (v1.0 and v1.1) ships 6D poses in **OpenGL/Blender camera convention** (camera looks down `-Z`, in-front objects have `cam_t_m2c.z < 0`) rather than the BOP-standard **OpenCV convention** (camera looks down `+Z`, in-front objects have `cam_t_m2c.z > 0`). The two differ by the basis change `diag(1, -1, -1)` applied to the camera frame.
+This release (v1.0 and v1.1) ships 6D poses in **OpenGL camera convention** (camera looks down `-Z`, in-front objects have `cam_t_m2c.z < 0`) rather than the BOP-standard **OpenCV convention** (camera looks down `+Z`, in-front objects have `cam_t_m2c.z > 0`). The two differ by the basis change `diag(1, -1, -1)` applied to the camera frame.
 
 **Anyone scoring against bop_toolkit_lib, MegaPose, FoundationPose, CosyPose, or any OpenCV-convention model must apply `diag(1, -1, -1)` to the GT `cam_R_m2c` and `cam_t_m2c` from `scene_gt.json` before evaluation**, otherwise pose errors blow up to the order of the object diameter (~150 mm) and any AR comparison is meaningless.