Align recommended target package names (#247)

abapGit · Aug 23, 2024 · f63ef0b · f63ef0b
1 parent ea272fb
commit f63ef0b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/development-guide/read-first/contributing.md b/src/development-guide/read-first/contributing.md
@@ -14,7 +14,7 @@ Having already [installed](/user-guide/getting-started/install.md#install-standa
 1. [Install the development version](/user-guide/getting-started/install.md#install-developer-version) of abapGit, by running `ZABAPGIT_STANDALONE` and either:
    1. cloning your *own [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)* of the [abapGit repository](https://github.com/abapGit/abapGit) using abapGit's "New Online" option or
    2. [downloading the zip file and installing it](/user-guide/getting-started/install.md#install-developer-version) using the "New Offline" option
-2. When specifying a package for the repository in step 1, assign a different (new, e.g. `$ZABAPGIT`) package to the one `ZABAPGIT_STANDALONE` is in
+2. When specifying a package for the repository in step 1, assign a different (new, e.g. `$ABAPGIT`) package to the one `ZABAPGIT_STANDALONE` is in
 
 3. Your system will now contain the abapGit package, along with several sub-packages and development objects such as classes, interfaces, function groups, etc. There will also be the development version of the abapGit program (transaction `ZABAPGIT`). The standalone program, `ZABAPGIT_STANDALONE` will remain unaffected, to serve as [fallback](/user-guide/getting-started/upgrade.md#troubleshooting).
 

diff --git a/src/user-guide/getting-started/install.md b/src/user-guide/getting-started/install.md
@@ -30,7 +30,7 @@ You can check your system for recommended SAP Notes using [Note Analyzer](/user-
 3. In source code change mode, upload the code from the file using Utilities -> More Utilities -> Upload/Download -> Upload
 4. Activate
 
-Typically, abapGit will only be used in the development system, so it can be installed in a local `$` package (e.g.  `$ZABAPGIT`).
+Typically, abapGit will only be used in the development system, so it can be installed in a local `$` package (e.g.  `$ABAPGIT`).
 
 Now you can use abapGit by executing the report in transaction `SE38`.