From 4f0c4ba68612f57883a4a9d185378365e7e6b372 Mon Sep 17 00:00:00 2001 From: Ahmed TAILOULOUTE Date: Thu, 2 Mar 2017 00:23:19 +0000 Subject: [PATCH] Fix typos --- components/cache/cache_invalidation.rst | 2 +- workflow.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/components/cache/cache_invalidation.rst b/components/cache/cache_invalidation.rst index 443700e1bf1..2f7814b8ff6 100644 --- a/components/cache/cache_invalidation.rst +++ b/components/cache/cache_invalidation.rst @@ -7,7 +7,7 @@ Cache Invalidation Cache invalidation is the process of removing all cached items related to a change in the state of your model. The most basic kind of invalidation is direct -items deletion. But when the state of a primary resource has spread accross +items deletion. But when the state of a primary resource has spread across several cached items, keeping them in sync can be difficult. The Symfony Cache component provides two mechanisms to help solving this problem: diff --git a/workflow.rst b/workflow.rst index 766c8ab2a7c..a1264bab91e 100644 --- a/workflow.rst +++ b/workflow.rst @@ -7,7 +7,7 @@ a user submits a series of different forms to complete a task. Such processes ar best kept away from your models and should be defined in configuration. A **definition** of a workflow consist of places and actions to get from one -place to another. The actions are called **transistions**. A workflow does also +place to another. The actions are called **transitions**. A workflow does also need to know each object's position in the workflow. That **marking store** writes to a property of the object to remember the current place.