Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit f63ef0b

Browse files
authored
Align recommended target package names (#247)
1 parent ea272fb commit f63ef0b

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/development-guide/read-first/contributing.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Having already [installed](/user-guide/getting-started/install.md#install-standa
1414
1. [Install the development version](/user-guide/getting-started/install.md#install-developer-version) of abapGit, by running `ZABAPGIT_STANDALONE` and either:
1515
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
1616
2. [downloading the zip file and installing it](/user-guide/getting-started/install.md#install-developer-version) using the "New Offline" option
17-
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
17+
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
1818

1919
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).
2020

src/user-guide/getting-started/install.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ You can check your system for recommended SAP Notes using [Note Analyzer](/user-
3030
3. In source code change mode, upload the code from the file using Utilities -> More Utilities -> Upload/Download -> Upload
3131
4. Activate
3232

33-
Typically, abapGit will only be used in the development system, so it can be installed in a local `$` package (e.g. `$ZABAPGIT`).
33+
Typically, abapGit will only be used in the development system, so it can be installed in a local `$` package (e.g. `$ABAPGIT`).
3434

3535
Now you can use abapGit by executing the report in transaction `SE38`.
3636

0 commit comments

Comments
 (0)