github#36243

content/actions/use-cases-and-examples/building-and-testing/building-and-testing-python.md

@@ -45,6 +45,7 @@ We recommend that you have a basic understanding of Python, and pip. For more in
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.actions.new-starter-workflow %}
+
 1. The "Choose a workflow" page shows a selection of recommended workflow templates. Search for "Python application".
 1. On the "Python application" workflow, click **Configure**.
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md

@@ -47,6 +47,7 @@ By default, the restrictions of a branch protection rule don't apply to people w
 ## About branch protection settings
 
 For each branch protection rule, you can choose to enable or disable the following settings.
+
 * [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
 * [Require status checks before merging](#require-status-checks-before-merging)
 * [Require conversation resolution before merging](#require-conversation-resolution-before-merging)
@@ -123,6 +124,8 @@ When you enable required commit signing on a branch, contributors {% ifversion f
 
 > [!NOTE]
 {% ifversion fpt or ghec %}
+>
+>
 > * If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see [AUTOTITLE](/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits).
 > * If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
 {% else %}