Fix migration guide mistakes (Azure#1564)

ngastelum-ms · Jun 30, 2022 · d659d3c · d659d3c
1 parent 702747a
commit d659d3c
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/SDK v2 migration guide.md b/SDK v2 migration guide.md
@@ -155,7 +155,8 @@ This client has been removed in v2. It is replaced by the MultiplexingClient. Se
 | DeviceTwin   | TwinClient  |
 | DeviceMethod |  DirectMethodsClient | 
 | ServiceClient   | MessagingClient, FileUploadNotificationProcessorClient, MessageFeedbackProcessorClient   |   
-| JobClient  |  BlockBlobClient, RegistryClient  |  
+| JobClient  |  ScheduledJobClient, RegistryClient  |  
+| Query, RawTwinQuery | QueryClient |
 
 For v1 classes with more than one equivalent v2 classes, the methods that were in the v1 class have been split up to 
 create clients with more cohesive capabilities. For instance, configurations CRUD was in the v1 RegistryManager, but has 
@@ -413,4 +414,4 @@ Question:
 > Is the v2 library backwards compatible in any way?
 
 Answer:
-> No. Several APIs have been added to v2 that are not present in v1. On top of that, several APIs in v2 are expected to behave differently than they did in v1.
+> No. Several APIs have been added to v2 that are not present in v1. On top of that, several APIs in v2 are expected to behave differently than they did in v1.