From abbadf4258c78faff4b86a9bada2521ef686306d Mon Sep 17 00:00:00 2001 From: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com> Date: Tue, 31 Jan 2023 11:42:37 -0800 Subject: [PATCH] Fix stop signal command Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com> --- .../resiliency-serviceinvo-quickstart.md | 21 ------------------- 1 file changed, 21 deletions(-) diff --git a/daprdocs/content/en/getting-started/quickstarts/resiliency/resiliency-serviceinvo-quickstart.md b/daprdocs/content/en/getting-started/quickstarts/resiliency/resiliency-serviceinvo-quickstart.md index 66808210e..05d87b0d3 100644 --- a/daprdocs/content/en/getting-started/quickstarts/resiliency/resiliency-serviceinvo-quickstart.md +++ b/daprdocs/content/en/getting-started/quickstarts/resiliency/resiliency-serviceinvo-quickstart.md @@ -149,31 +149,10 @@ Since the `resiliency.yaml` spec defines the `order-processor` service as a resi In the `order-processor` window, stop the service: -{{< tabs "MacOs" "Windows" >}} - - - -{{% codetab %}} - -```script -CMD + C -``` - -{{% /codetab %}} - - - -{{% codetab %}} - ```script CTRL + C ``` -{{% /codetab %}} - -{{< /tabs >}} - - Once the first request fails, the retry policy titled `retryForever` is applied: ```bash