docs: add info reusable workflow inputs always string vars

docs/intro.md

@@ -127,6 +127,11 @@ As you can see, `uses` is to define the workflow you want to run:
 The `with` key is used to specify all of the **inputs** to pass to the workflow.
 (these are predefined by the creator of the reusable workflow).
 
+> Note that inputs are **always** string variables.
+> So keep this in mind when creating conditionals (use inputs.var == 'true').
+>
+> The `type` field is not supported for reusable workflow inputs, yet.
+
 ### Using Secrets in Reusable Workflows
 
 By default reusable workflows will not have access to environment
@@ -136,23 +141,23 @@ There are two ways to do this:
 
 1. Specify secrets individually:
 
-```yaml
-jobs:
-  pytest:
-    uses: hotosm/gh-workflows/.github/workflows/some_workflow.yml@main
-    secrets:
-      SECRET_VAR_1: ${{ secrets.SECRET_VAR_1 }}
-      SECRET_VAR_2: ${{ secrets.SECRET_VAR_2 }}
-```
+   ```yaml
+   jobs:
+     pytest:
+       uses: hotosm/gh-workflows/.github/workflows/some_workflow.yml@main
+       secrets:
+         SECRET_VAR_1: ${{ secrets.SECRET_VAR_1 }}
+         SECRET_VAR_2: ${{ secrets.SECRET_VAR_2 }}
+   ```
 
 2. Inherit all secrets (recommended):
 
-```yaml
-jobs:
-  pytest:
-    uses: hotosm/gh-workflows/.github/workflows/some_workflow.yml@main
-    secrets: inherit
-```
+   ```yaml
+   jobs:
+     pytest:
+       uses: hotosm/gh-workflows/.github/workflows/some_workflow.yml@main
+       secrets: inherit
+   ```
 
 ## Passing Info Between Workflows