From 9243a41f9771b17cd9810058d578db51f5962d1e Mon Sep 17 00:00:00 2001
From: Robert Cannon <rpcann@gmail.com>
Date: Fri, 21 May 2021 13:28:43 -0400
Subject: [PATCH] Re-order example descriptions (#209)

Given the way that the two descriptions were written it was confusing about which example was being discussed (see specifically "In the above example in the previous version).
---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 7ce4e17..316b5db 100644
--- a/README.md
+++ b/README.md
@@ -125,7 +125,7 @@ If not provided, `artifact` will be used as the default name which will manifest
 
 ### Uploading to the same artifact
 
-Each artifact behaves as a file share. Uploading to the same artifact multiple times in the same workflow can overwrite and append already uploaded files
+With the following example, the available artifact (named `artifact` by default if no name is provided) would contain both `world.txt` (`hello`) and `extra-file.txt` (`howdy`).
 
 ```yaml
 - run: echo hi > world.txt
@@ -143,10 +143,11 @@ Each artifact behaves as a file share. Uploading to the same artifact multiple t
   with:
     path: world.txt
 ```
-With the following example, the available artifact (named `artifact` which is the default if no name is provided) would contain both `world.txt` (`hello`) and `extra-file.txt` (`howdy`).
 
 > **_Warning:_**  Be careful when uploading to the same artifact via multiple jobs as artifacts may become corrupted 
 
+Each artifact behaves as a file share. Uploading to the same artifact multiple times in the same workflow can overwrite and append already uploaded files
+
 ```yaml
     strategy:
       matrix: