docs(unifi): resolve review leftovers

apps/docs/docs/integrations/unifi-controller/index.mdx

@@ -16,7 +16,7 @@ import { networkControllerStatusWidget } from "@site/docs/widgets/network-contro
 <IntegrationHeader integration={unifiControllerIntegration} categories={["Network controller"]} />
 
 This integration is using the [node-unifi](https://www.npmjs.com/package/node-unifi) library under the hood to connect to the Unifi Controller.
-Therfore it should support CloudKey Gen1, CloudKey Gen2, UnifiOS-based UDM-Pro controllers as well as self-hosted UniFi controllers.
+Therefore it should support CloudKey Gen1, CloudKey Gen2, UnifiOS-based UDM-Pro controllers as well as self-hosted UniFi controllers.
 
 ### Widgets & Capabilities
 

packages/integrations/src/unifi-controller/unifi-controller-integration.ts

@@ -66,7 +66,7 @@ export class UnifiControllerIntegration extends Integration implements NetworkCo
       checkServerIdentity: createCustomCheckServerIdentity(await getTrustedCertificateHostnamesAsync()),
     };
 
-    // ponytail: node-unifi always connects over HTTPS, regardless of the protocol in the
+    // node-unifi always connects over HTTPS, regardless of the protocol in the
     // integration URL. UniFi OS consoles use port 443 while self-hosted controllers normally
     // use 8443. If no port was provided, try both without hiding authentication errors.
     const ports = url.port ? [Number(url.port)] : [443, 8443];