Fix docs

Author: dstamand-msft

docs/github-app-setup.md

@@ -1,4 +1,4 @@
-# GitHub App Setup
+                             # GitHub App Setup
 
 The following steps will guide you through the process of setting up a GitHub App for the project. This setup is essential for the bot to function correctly and interact with GitHub's WebHook events.
 
@@ -53,7 +53,7 @@ In the General settings of the GitHub App, scroll down to the Display informatio
 In the App managers section of the GitHub App, you can add users who will be able to manage the app. This includes users who can install the app, view the app's settings, and manage the app's permissions. You can add users by their GitHub username or full name. This is optional, but it is recommended to add at least one user who will be responsible for managing the app.
 
 ### Step 1.5: Install the App
-In the organization settings, under the developer settings, click on GitHub Apps. Next to the GitHub App that you want to install, click Edit. Click Install App. Click Install next to the location where you want to install the GitHub App.
+In the organization settings, under the developer settings, click on GitHub Apps. Next to the GitHub App that you want to install, click Edit. Click Install App. Click Install next to the location where you want to install the GitHub App. Choose All Repositories.
 
 ### Step 1.6: Configure the repository access
 In the organization settings, under Third party-access, in the GitHub Apps section, Click on the "configure" button next to your app. In the repository access section, select **All repositories**.
@@ -65,7 +65,7 @@ In the repository that will be used for onboarding (the ones that has the issue
 - **APPROVED**: Support ticket approved and will be processed (Color: #7EF299)
 - **COMPLETED**: Support ticket completed (Color: #0E8A16)
 - **FAILED**: Validation checks failed (Color: #B60205)
-- **OPENE**D: Support ticket opened (Color: #1D76DB)
+- **OPENED**: Support ticket opened (Color: #1D76DB)
 - **REJECTED**: Support ticket rejected and will be closed automatically (Color: #E99695)
 - **VALIDATED**: Validation checks passed and configuration as code will be created (Color: #006B75)
 
@@ -74,18 +74,18 @@ You can also get to this page by navigating to the following page: `https://gith
 ### Step 2.2: Create the custom properties
 In the organization settings, under Repository, click on "Custom properties". Click on **New property** for each property listed below. Replace the placeholder with your appropriate values.
 **Ruleset property**<br/>
-- **Name**: <Name>-Ruleset
-- **Description**: The rulesets applied to repository using the <GitHub App name> App.
+- **Name**: \<Name\>-Ruleset
+- **Description**: The rulesets applied to repository using the \<GitHub App name\> App.
 - **Type**: Multi select
 	- Options: add as many as you see fit, depending on how many rulesets you plan to have.
-		- **<GitHub App name>-Ruleset-Default**: The default ruleset that can be applied to all repositories
+		- **\<GitHub App name\>-Ruleset-Default**: The default ruleset that can be applied to all repositories
 - Check the box for **Allow repository actors to set this property**.
 - Check the box for **Require this property for all repositories** and pick the default value to the default value that you have set in the options above.
 
-**<Name> property**<br/>
+**\<Name\> property**<br/>
 This property is used as a flag to indicate that the repository was onboarded using the GitHub App.<br/>
-- **Name**: <Name>
-- **Description**: Flag to indicate that the repository was onboarded using the <GitHub App name> App
+- **Name**: \<Name\>
+- **Description**: Flag to indicate that the repository was onboarded using the \<GitHub App name\> App
 - **Type**: true/false
 - Check the box for **Allow repository actors to set this property**.
 - Check the box for **Require this property for all repositories** and pick the default value to the default value that you have set 
@@ -94,3 +94,4 @@ This property is used as a flag to indicate that the repository was onboarded us
 In the organization settings, under Repository, click on "Rulesets". Click on "New ruleset". Select the ruleset type ou want to create whether they are branch ruleset, tag ruleset or push ruleset.<br/><br/>
 We strongly recommend to create a ruleset with the following configuration:<br/><br/>
 In Targets, under the Target repositories, pick the target **Dynamic list by property**. For the property, select the property create in Step 2.2. For the value, select the value **GitHub App**. This will ensure that the ruleset is applied to all repositories that have the property GitHub App set to GitHub App.
+The ruleset enforcement status should be set to **Active**.

docs/main.md

@@ -35,7 +35,7 @@ This application is built using .NET Core. It supports multiple data stores, inc
 | `Azure:AzureMonitor:EnableTelemetry`     | String | Whether to enable telemetry or not.                                         |
 | `Azure:AzureMonitor:UseEntraIdAuthentication` | String | When telemetry is enabled, whether to use entra for authentication vs Instrumentation Key. |
 | `DataStore:Type`                         | String | Type of data store (FileSystem, CosmosDb, SqlServer).                       |
-| `DataStore:FileSystem:FilePath`          | String | File path for file system data store.                                       |
+| `DataStore:FileSystem:FilePath`          | String | File path for file system data store. This is a directory.                                       |
 | `DataStore:CosmosDb:Database`            | String | Database name for Cosmos DB.                                                |
 | `DataStore:CosmosDb:ConnectionString`    | String | Connection string for Cosmos DB.                                            |
 | `DataStore:CosmosDb:GitHubWebhooksContainer` | String | Container for GitHub webhooks in Cosmos DB.                             |
@@ -118,4 +118,9 @@ Follows the .NET FeatureManagement [schema](https://learn.microsoft.com/en-us/az
 
 ## [GitHub setup](#github-setup)
 
-Before you can use the GitHub DevEx Accelerator, you need to set up a GitHub App and configure it with the necessary permissions. Please follow the guide [here](./docs/github-app-setup.md) to do so.
+Before you can use the GitHub DevEx Accelerator, you need to set up a GitHub App and configure it with the necessary permissions. Please follow the guide [here](./docs/github-app-setup.md) to do so.
+
+You will also need to create 3 repositories in your organization:
+- **\<onboarding-repository-name\>**: This repository will be used for onboarding. It should contain the issue templates that will be used for onboarding.
+- **\<inventory-repository-name\>**: This repository will be used for inventory. It will contain the inventory metadata.
+- **\<policy-repository-name\>**: This repository will be used for the policies. It will contain the policies metadata.