Fix typos

MicrosoftDocs · Dec 1, 2023 · ed122d3 · ed122d3
1 parent f6e0efe
commit ed122d3
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/msal-java-articles/advanced/exceptions.md b/msal-java-articles/advanced/exceptions.md
@@ -32,7 +32,7 @@ MSAL exposes a `reason` field, which you can read to provide a better user exper
 |MessageOnly|Condition can't be resolved at this time. Launching interactive authentication flow will show a message explaining the condition.| Call acquireToken with interactive parameters to show a message that explains the condition. acquireTokenCall will return UserCanceled error after the user reads the message and closes the window. Calling application may choose to hide flows that result in message_only if the user is unlikely to benefit from the message.|
 |ConsentRequired|User consent is missing, or has been revoked.|Call all acquireToken with interactive parameters for user to give consent.|
 |UserPasswordExpired|User's password has expired.|Call acquireToken with interactive parameter so user can reset password|
-|ConsentRequired|User consent is missing, or has been revoked| Call acquireToken with interactive paramaters so user can reset password|
+|ConsentRequired|User consent is missing, or has been revoked| Call acquireToken with interactive parameters so user can reset password|
 |None| 	No further details are provided. Condition may be resolved by user interaction during the interactive authentication flow. | Call acquireToken with interactive parameters|
 
 ## Code Example

diff --git a/msal-java-articles/advanced/msal-java-token-cache-serialization.md b/msal-java-articles/advanced/msal-java-token-cache-serialization.md
@@ -14,7 +14,7 @@ To persist the token cache between instances of your application, you will need
 Below is a naive implementation of custom serialization of the token cache.
 
 >[!WARNING]
->Because the sample cod ebelow doesn't showcase the full cache storage lifecycle, we strongly recomment to not copy and paste this into a production environment. Make sure that you're aware of security and access requirements for the token cache.
+>Because the sample code below doesn't showcase the full cache storage lifecycle, we strongly recommend to not copy and paste this into a production environment. Make sure that you're aware of security and access requirements for the token cache.
 
 ```java
 static class TokenPersistence implements ITokenCacheAccessAspect {

diff --git a/msal-java-articles/advanced/using-wam-and-the-msal4jbrokers-package.md b/msal-java-articles/advanced/using-wam-and-the-msal4jbrokers-package.md
@@ -74,4 +74,4 @@ Although the API for enabling a broker is very simple, a number of packages are
 
 - [msal4j-brokers](https://mvnrepository.com/artifact/com.microsoft.azure/msal4j-brokers) - Essentially a thin layer between msal4j and javamsalruntime, meant to handle the conversion between requests from msal4j and results from javamsalruntime
 - [javamsalruntime](https://mvnrepository.com/artifact/com.microsoft.azure/javamsalruntime) - A Java project that uses [JNA](https://mvnrepository.com/artifact/com.microsoft.azure/javamsalruntime) to call into native code, converting Java classes and variables into C#/C++ equivalents and vice versa
-- MSALRruntime - A C++/C# project that provides APIs for accessing WAM and a number of other features, and eventually other auth brokers. This project produces the dll packages that javamsalruntime calls via JNA, and is the ultimate decider for what scenarios msal4j-brokers can support
+- MSALRuntime - A C++/C# project that provides APIs for accessing WAM and a number of other features, and eventually other auth brokers. This project produces the dll packages that javamsalruntime calls via JNA, and is the ultimate decider for what scenarios msal4j-brokers can support