Respond to feedback about leaving raw logging enabled

Andy Piper was concerned that this might be interpreted as a recommendation to leave raw logging on all the time. Tried to clarify that it should only be enabled while turning.

common/source/docs/common-imu-batchsampling.rst

@@ -92,7 +92,7 @@ Advanced Configuration and Analysis
 - :ref:`INS_LOG_BAT_LGIN <INS_LOG_BAT_LGIN>` interval between pushing samples to the dataflash log, in ms.  Increase this to reduce the time taken to flush data to the dataflash log, reducing cycle time.  This will be at the expense of increased system load and possibly choking up the dataflash log for other messages
 - :ref:`INS_LOG_BAT_LGCT <INS_LOG_BAT_LGCT>` Number of samples to push to count every :ref:`INS_LOG_BAT_LGIN <INS_LOG_BAT_LGIN>` ms.  Increase this to push more samples each time they are sent to the dataflash log.  Increasing this may cause timing jitter, and possibly choke up the dataflash log for other messages
 
-.. note:: On an H7 based autopilot such as the CubeOrange or Zealot H743, raw IMU logging can be used and will provide better data for analysis. Set INS_LOG_BITMASK = 0 and sent the raw IMU bit (bit 19) in LOG_BITMASK.
+.. note:: On an H7 based autopilot such as the CubeOrange or Zealot H743, raw IMU logging can be used and will provide better data for analysis. Set INS_LOG_BITMASK = 0 and sent the raw IMU bit (bit 19) in LOG_BITMASK. Raw logging is very helpful when doing filter tuning, but will give you really large logs which generally means you don't want to leave it on. Batch logging on the other hand can be left on all the time which helps with ad-hoc analysis. 
 
 The web based `Notch Filter Review tool <https://firmware.ardupilot.org/Tools/WebTools/FilterReview/>`on the ArduPilot Firmware "Web Tools" page can be used to analyse notch filter logs generated with either batch sampling or raw IMU logging.