Merge branch 'main' into mbtools/abap-lang-vers

Author: mbtools

src/user-guide/projects/online/first-project.md

@@ -6,20 +6,30 @@ order: 40
 
 ## Repository Setup 
 
-* Create the repsitory on GitHub, make sure it contains someting eg. a README file
+* Create the repository on GitHub, and make sure it contains something like a README file
 * Start `ZABAPGIT`
 * Clone the repository into abapGit
 
 ## Adding Objects
 
-* Navigate to the repository, click the "add" link
-* It will ask which object to add, select the object
-* The object will be commited to the repository
+* Navigate to the repository, click the "Add" link
+* It will ask which object to add, then select the object
+* The object will be committed to the repository
 
 ## Modifying Objects
 
-After modifying a object, a "commit" link will show up in abapGit, click this to commit the changes to the remote repository.
+After modifying an object, a "commit" link will show up in abapGit. Click this to commit the changes to the remote repository.
 
 ## Modifying Repository
 
-If something is changed in the repository, a "pull" link will show up in abapGit. The changes must be pulled before new objects can be changed or added.
+If something is changed in the repository, a "pull" link will show up in abapGit. The changes must be pulled before new objects can be changed or added.
+
+## Handling Licenses
+
+Open-source projects on GitHub typically include a `LICENSE` file that describes the repository's licensing terms.
+
+:::info
+Note: This license file will not be pulled into SAP systems by abapGit. 
+
+If your license requires, include the license terms in the comments of your main source code file. Alternatively, you can reference the license using an [SPDX License Identifier](https://spdx.dev/learn/handling-license-info/). 
+:::

src/user-guide/reference/flow.md

@@ -4,4 +4,17 @@ category: reference
 order: 90
 ---
 
-BETA feature, use this if you know what you are doing
+BETA FEATURE
+
+The abapGit flow page helps mirroring branches/pull requests into/from transports by doing filtered git operations. This way, it is possible to work on multiple branches in one system, or pull multiple branches into a system.
+
+:::warning
+Filtered git operations is not a real git thing, its something else than git. It is a workable compromise to work with git in a multi user system
+:::
+
+The flow page gives an overview of all features that a developer is working on across their favorite repositories.
+
+## Enabling
+
+To enable a repository to work with flow, go to the local repository settings and tick "Flow Page".
+Furthermore, developers must set their favorite repositories, so abapGit knows which parts each developer is working on.