From ebc07828684ef12c55fe1d88b836926ff06713e5 Mon Sep 17 00:00:00 2001 From: Joshua Harlow Date: Sat, 4 Apr 2015 19:45:33 -0700 Subject: [PATCH] Put semantics preservation section into note block Change-Id: I2fceb1628ef384f6d5db1f292cabe48195efbf9c --- doc/source/engines.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/source/engines.rst b/doc/source/engines.rst index 5225f96f..9563cb45 100644 --- a/doc/source/engines.rst +++ b/doc/source/engines.rst @@ -17,11 +17,13 @@ and *ideal* is that deployers or developers of a service that use TaskFlow can select an engine that suites their setup best without modifying the code of said service. -Engines usually have different capabilities and configuration, but all of them -**must** implement the same interface and preserve the semantics of patterns -(e.g. parts of a :py:class:`.linear_flow.Flow` -are run one after another, in order, even if the selected engine is *capable* -of running tasks in parallel). +.. note:: + + Engines usually have different capabilities and configuration, but all of + them **must** implement the same interface and preserve the semantics of + patterns (e.g. parts of a :py:class:`.linear_flow.Flow` + are run one after another, in order, even if the selected + engine is *capable* of running tasks in parallel). Why they exist --------------