|
14 | 14 | // Flutter features, like application lifecycle handling. |
15 | 15 | @implementation FlutterApplication |
16 | 16 |
|
17 | | -// Initialize NSApplication using the custom subclass. Check whether NSApp was |
| 17 | +// Initialize NSApplication using the custom subclass. Check whether NSApp was |
18 | 18 | // already initialized using another class, because that would break some |
19 | 19 | // things. Warn about the mismatch only once, and only in debug builds. |
20 | 20 | + (NSApplication*)sharedApplication { |
@@ -47,7 +47,7 @@ + (NSApplication*)sharedApplication { |
47 | 47 | // and shutdown. |
48 | 48 | // |
49 | 49 | // We override the normal |terminate| implementation. Our implementation, which |
50 | | -// is specific to the asyncronous nature of Flutter, works by asking the |
| 50 | +// is specific to the asynchronous nature of Flutter, works by asking the |
51 | 51 | // application delegate to terminate using its |requestApplicationTermination| |
52 | 52 | // method instead of going through |applicationShouldTerminate|. |
53 | 53 | // |
@@ -77,7 +77,7 @@ - (void)terminate:(id)sender { |
77 | 77 | exitType:kFlutterAppExitTypeCancelable |
78 | 78 | result:nil]; |
79 | 79 | // Return, don't exit. The application delegate is responsible for exiting on |
80 | | - // its own by calling |-terminateApplication|. |
| 80 | + // its own by calling |terminateApplication|. |
81 | 81 | } |
82 | 82 |
|
83 | 83 | // Starts the regular Cocoa application termination flow, so that plugins will |
|
0 commit comments