From e04e416e4576a8c4cf801e983ee5c7f5e608bd0c Mon Sep 17 00:00:00 2001 From: sorinj Date: Mon, 9 Mar 2020 14:17:29 -0700 Subject: [PATCH] Update CustomizingOmaha.md --- doc/CustomizingOmaha.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/CustomizingOmaha.md b/doc/CustomizingOmaha.md index aa77bd2b2..bc7679142 100644 --- a/doc/CustomizingOmaha.md +++ b/doc/CustomizingOmaha.md @@ -20,7 +20,7 @@ The following items **MUST** be changed before releasing a fork of Omaha. Prefe > Modify **`kGlobalPrefix`** at the top of the file to contain your company name. - * **`omaha\base\const_goopdate.h`** + * **`omaha\common\const_goopdate.h`** > Modify the names of the service names (examples: **`omaha_task_name_c`**, **`omaham_service_name`**, etc.) to contain your product's name. @@ -61,4 +61,4 @@ We strongly recommend making these changes before you release: The version number stored in all outputs is set in the file **`omaha\VERSION`**. Omaha has some functionality in it from Google Update related to bug workarounds when upgrading from prior versions, so don't set the VERSION to any lower than 1.3.23.0. -When releasing your fork of Omaha, we recommend starting the version at 1.3.25.0. Remember to bump the version up whenever releasing an updated version. \ No newline at end of file +When releasing your fork of Omaha, we recommend starting the version at 1.3.25.0. Remember to bump the version up whenever releasing an updated version.