#471 (#490)

* Fixed documentation

* Modified the allow_private description

* Update README.md

Signed-off-by: AshitaSingamsetty <[email protected]>

* Update actions.md

Signed-off-by: AshitaSingamsetty <[email protected]>

* Removed a word

---------

Signed-off-by: AshitaSingamsetty <[email protected]>
Co-authored-by: Singamsetty Venkata,Ashita <[email protected]>
Co-authored-by: AshitaSingamsetty <[email protected]>
Co-authored-by: AshitaSingamsetty <[email protected]>

Author: 3 people

docs/actions.md

@@ -21,9 +21,8 @@ A bit more about the different fields...
 - `allow_private` (optional)
     - bool [true, false]
     - default: false
-    - If false bugs that are not public will not be synchronized. Note that in order to synchronize
-      private bugs the bugzilla user that JBI runs as must be in the security groups that are making
-      the bug private.
+    - If `false`, bugs will not be synchronized if they are not public. Note that in order to synchronize private bugs,
+     the bugzilla user that JBI runs as must be in the security groups that are making the bug private.
 - `bugzilla_user_id`
     - a bugzilla user id, a list of user ids, or a literal "tbd" to signify that no bugzilla user id is available
     - If an issue arises with the workflow, communication will be established with these users