removed more whitespaces

index.bs

@@ -321,8 +321,7 @@ credentials by [=web applications=], for the purpose of strongly authenticating
 created and stored by a <em>[=[WAA]=]</em> at the behest of a <em>[=[WRP]=]</em>, subject to <em>[=user
 consent=]</em>. Subsequently, the [=public key credential=] can only be accessed by [=origins=] belonging to that [=[RP]=].
 This scoping is enforced jointly by <em>[=conforming User Agents=]</em> and <em>[=authenticators=]</em>.
-Additionally, privacy across [=[RPS]=] is maintained; [=[RPS]=] are not able to detect any properties, or even
-the existence, of credentials [=scoped=] to other [=[RPS]=]. 
+Additionally, privacy across [=[RPS]=] is maintained; [=[RPS]=] are not able to detect any properties, or even the existence, of credentials [=scoped=] to other [=[RPS]=]. 
 
 [=[RPS]=] employ the [=Web Authentication API=] during two distinct, but related, [=ceremonies=] involving a user. The first
 is [=Registration=], where a [=public key credential=] is created on an [=authenticator=], and [=scoped=] to a [=[RP]=]
@@ -364,8 +363,7 @@ Beyond that, the intended audiences for this document are the following main gro
         Additionally, if they intend to verify [=authenticator=] [=attestations=], then
         [[#sctn-attestation]] and [[#sctn-defined-attestation-formats]] will also be relevant.
         [[#sctn-extensions]], and [[#sctn-defined-extensions]] will be of interest if they wish to make use of extensions.
-        Finally, they should read [[#sctn-security-considerations-rp]] and [[#sctn-privacy-considerations-rp]]
-        and consider which challenges apply to their application and users. 
+        Finally, they should read [[#sctn-security-considerations-rp]] and [[#sctn-privacy-considerations-rp]] and consider which challenges apply to their application and users. 
 
 - User agent developers
 - OS platform developers, responsible for OS platform API design and implementation in regards to platform-specific