[BUGFIX] Updated class name in scheduler docs 83/55683/2
authorMichael Oehlhof <typo3@oehlhof.de>
Sun, 17 Dec 2017 23:34:48 +0000 (00:34 +0100)
committerChristian Kuhn <lolli@schwarzbu.ch>
Mon, 12 Feb 2018 16:27:35 +0000 (17:27 +0100)
Resolves: #66587
Releases: master, 8.7
Change-Id: If5fbb4df430aeb08122cc0713167a8cc464e6d55
Reviewed-on: https://review.typo3.org/55683
Reviewed-by: Frank Naegler <frank.naegler@typo3.org>
Tested-by: Frank Naegler <frank.naegler@typo3.org>
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
typo3/sysext/scheduler/Documentation/AppendixA/Index.rst

index d2a8946..f510c0a 100644 (file)
@@ -27,7 +27,7 @@ table.
 
 That being said, a task also contains information about its execution.
 Indeed each task class has an instance of
-:code:`tx_scheduler_Execution` as a member variable, which contains
+:code:`TYPO3\CMS\Scheduler\Execution` as a member variable, which contains
 information such as start and end date and is used to calculate the
 next execution date.
 
@@ -36,6 +36,6 @@ is serialized and stored in the corresponding database record. If
 several executions are running at the same time, the array will
 contain several timestamps. Thus the "serialized\_executions" field
 actually contains an array of integers and not serialized instances of
-:code:`tx_scheduler_Execution` objects.
+:code:`TYPO3\CMS\Scheduler\Execution` objects.