From 23cafed0e0e0fbdd24fd1b144e241752c1684242 Mon Sep 17 00:00:00 2001
From: KBR <57449423+kbr-odoo@users.noreply.github.com>
Date: Tue, 3 Nov 2020 12:07:39 +0100
Subject: [PATCH] [IMP] timesheets: get_started.rst (#780)

Under the title 'Choose an enconding unit', a piece of information was added explaining that the minimal duration and rounding minutes are applied to times added when using the timer, clarifying that it does not apply for manual entries.
---
 timesheets/overview/get_started.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/timesheets/overview/get_started.rst b/timesheets/overview/get_started.rst
index 1e4ad7c04..d43b9d1e1 100644
--- a/timesheets/overview/get_started.rst
+++ b/timesheets/overview/get_started.rst
@@ -12,10 +12,10 @@ Choose an encoding unit
 
 | Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the unit of measure to
   register your timesheet. This provides tools and widgets to help you encoding.
-| *Minimal duration* is the minimum time at which a task is recorded.
-| *Rounding up* allows you to time up or down to the nearest minutes or hours. For example: if the
-  interval is set to 30min, a 14min entry will show up in reports as 0min, and a 29min entry
-  as 30min.
+| *Minimal duration* is the minimum time at which a task is recorded, when using the timer.
+| *Rounding up* times up or down to the nearest minutes or hours, when using the timer.
+   For example: if the interval is set to 30min, a 14min entry shows up in reports as 0min, and
+   a 29min entry as 30min.
 
 .. image:: media/get1.png
    :align: center