Potpourri (#714)

* enterprise policy typo

* more generic language in fido doc

* missing paren

* replace apr image with gif, profit

* fix language that ain't friendly to non-native english speakers (TY @Greenderella)

* faq item for mp hint

* windows firewall exclusion tip

* update cert article w/ powershell instructions for new letsencrypt cert

* improve collection header

* note on self-host server release lag

* duo bypass code tip

* revert

_articles/organizations/about-collections.md

@@ -53,7 +53,7 @@ Nested Collections are **for display-purposes only**. They will not inherit item
 
 To create a nested Collection, follow the [steps above](#create-a-collection), but give your Collections a **Name** that includes the "parent" name followed by a forward slash (`/`) delimiter, for example `Collection 1/Collection 1a`. If the "parent" Collection doesn't exist, the title will be displayed in-full.
 
-## Edit or Delete a Collection
+## Manage a Collection
 
 You may find that you need to add or remove users from a Collection, or delete it entirely. Both of these can be done from the **Manage** → **Collections** view by hovering over the desired Collection and selecting the {% icon fa-cog %} gear dropdown:
 

_articles/organizations/admin-reset.md

@@ -73,7 +73,7 @@ If you're automatically enrolling Organization members in Admin Password Reset,
 
 To enroll in Password Reset, navigate to **Settings** → **Organizations** in the [Web Vault](https://vault.bitwarden.com/){:target="\_blank"}:
 
-{% image organizations/pwreset-enroll.png Enroll in Password Reset %}
+{% image organizations/pwreset-enroll-gif.gif Enroll in Password Reset %}
 
 Hover over the Organization you wish to enroll in Password Reset for, select the {% icon fa-cog %} gear dropdown, and choose **Enroll in Password Reset**. When you're enrolled in Password Reset, the Organization listing will display a {% icon fa-key %} key icon. You can enroll in Admin Password Reset for multiple Organizations, if you choose.
 

_articles/organizations/policies.md

@@ -92,7 +92,7 @@ Enabling the **Single Sign-On Authentication** policy will require non-Owner/non
 {% callout info %}
 The **Single Organization** policy must be enabled before activating this policy.
 
-As a result, you must disable the **Single Sign-On Authentication** policy before you can disable the **Single Ownership** policy.
+As a result, you must disable the **Single Sign-On Authentication** policy before you can disable the **Single Organization** policy.
 {% endcallout %}
 
 ### Personal Ownership