From cc2573de76e1eebb04a990965b0d36ee0342116c Mon Sep 17 00:00:00 2001 From: Brendan Kidwell Date: Mon, 14 May 2012 12:56:24 -0400 Subject: [PATCH] markup fix --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4395037f..4853ee86 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ Committing New Progress and Pulling Changes from Other Developers Committing a New "Release" of Your Project ------------------------------------------ -1. There may be application changes that aren't covered in the source code for Forms, Macros, Modules, Queries, and Reports. To make sure these changes are recorded, Compact and Repair `Application.accdb` and zip it to `Application.zip` (replacing the old copy) using the Send to Compressed Folder command in Windows Explorer. Commit the new Application.zip to your repository with a commit message like "Full application binary for release [number]". +1. There may be application changes that aren't covered in the source code for Forms, Macros, Modules, Queries, and Reports. To make sure these changes are recorded, Compact and Repair `Application.accdb` and zip it to `Application.zip` (replacing the old copy) using the Send to Compressed Folder command in Windows Explorer. Commit the new `Application.zip` to your repository with a commit message like "Full application binary for release [number]". 2. Follow the usual steps in the previous section "Committing New Progress". 3. Use your repository's "tag" function to tag your last commit with the release number/name.