Skip to content

Commit ae3ed09

Browse files
authored
Fix some typos (#12760)
1 parent 16f64bf commit ae3ed09

File tree

11 files changed

+13
-13
lines changed

11 files changed

+13
-13
lines changed

.github/actions/notices_generation/app.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@
3838
begin
3939
OptionParser.new do |opts|
4040
opts.banner = "Usage: app.rb [options]"
41-
opts.on('-p', '--pods PODS', 'Pods seperated by space or comma.') { |v| @options[:pods] = v.split(/[ ,]/) }
41+
opts.on('-p', '--pods PODS', 'Pods separated by space or comma.') { |v| @options[:pods] = v.split(/[ ,]/) }
4242
opts.on('-s', '--sources SOURCES', 'Sources of Pods') { |v| @options[:sources] = v.split(/[ ,]/) }
4343
opts.on('-m', '--min_ios_version MIN_IOS_VERSION', 'Minimum iOS version') { |v| @options[:min_ios_version] = v }
4444
opts.on('-n', '--notices_path OUTPUT_PATH', 'The output path of NOTICES') { |v| @options[:output_path] = v }

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -361,7 +361,7 @@ viewing the [documentation][xcode-debugging].
361361
### Testing
362362

363363
Tests are an essential part to building Firebase. Many of the tests
364-
for Firebase run as part of our continous integration (CI) setup with
364+
for Firebase run as part of our continuous integration (CI) setup with
365365
[GitHub Actions].
366366

367367
* _Fixing a bug?_ Add a test to catch potential regressions in

Crashlytics/Crashlytics/Components/FIRCLSApplication.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ typedef NS_ENUM(NSInteger, FIRCLSApplicationInstallationSourceType) {
3232
};
3333

3434
/**
35-
* Returns the application bundle identifier with occurences of "/" replaced by "_"
35+
* Returns the application bundle identifier with occurrences of "/" replaced by "_"
3636
*/
3737
NSString* FIRCLSApplicationGetBundleIdentifier(void);
3838

Crashlytics/Crashlytics/Components/FIRCLSContext.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929

3030
// The purpose of the crash context is to hold values that absolutely must be read and/or written at
3131
// crash time. For robustness against memory corruption, they are protected with guard pages.
32-
// Further, the context is seperated into read-only and read-write sections.
32+
// Further, the context is separated into read-only and read-write sections.
3333

3434
__BEGIN_DECLS
3535

Crashlytics/Crashlytics/Components/FIRCLSProcess.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ static bool FIRCLSProcessGetThreadState(FIRCLSProcess *process,
173173
return true;
174174
}
175175

176-
// Here's a wild trick: emulate what thread_get_state would do. It apppears that
176+
// Here's a wild trick: emulate what thread_get_state would do. It appears that
177177
// we cannot reliably unwind out of thread_get_state. So, instead of trying, setup
178178
// a thread context that resembles what the real thing would look like
179179
if (FIRCLSProcessIsCurrentThread(process, thread)) {

Crashlytics/Crashlytics/Handlers/FIRCLSMachException.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ static exception_mask_t FIRCLSMachExceptionMask(void) {
9393
// is a confirmed kernel bug. Lacking access to EXC_CRASH means we must use signal handlers to
9494
// cover all types of crashes.
9595
// EXC_GUARD is relatively new, and isn't available on all OS versions. You have to be careful,
96-
// because you cannot successfully register hanlders if there are any unrecognized masks. We've
96+
// because you cannot successfully register handlers if there are any unrecognized masks. We've
9797
// dropped support for old OS versions that didn't have EXC_GUARD (iOS 5 and below, macOS 10.6 and
9898
// below) so we always add it now
9999

@@ -192,7 +192,7 @@ static bool FIRCLSMachExceptionReadMessage(FIRCLSMachExceptionReadContext* conte
192192
r = mach_msg(&message->head, MACH_RCV_MSG | MACH_RCV_LARGE, 0, sizeof(MachExceptionMessage),
193193
context->port, MACH_MSG_TIMEOUT_NONE, MACH_PORT_NULL);
194194
if (r != MACH_MSG_SUCCESS) {
195-
FIRCLSSDKLog("Error receving mach_msg (%d)\n", r);
195+
FIRCLSSDKLog("Error receiving mach_msg (%d)\n", r);
196196
return false;
197197
}
198198

Crashlytics/Crashlytics/Handlers/FIRCLSSignal.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ static void FIRCLSSignalInstallHandlers(FIRCLSSignalReadContext *roContext) {
8686
action.sa_sigaction = FIRCLSSignalHandler;
8787
// SA_RESETHAND seems like it would be great, but it doesn't appear to
8888
// work correctly. After taking a signal, causing another identical signal in
89-
// the handler will *not* cause the default handler to be invokved (which should
89+
// the handler will *not* cause the default handler to be involved (which should
9090
// terminate the process). I've found some evidence that others have seen this
9191
// behavior on MAC OS X.
9292
action.sa_flags = SA_SIGINFO | SA_ONSTACK;

Crashlytics/Crashlytics/Helpers/FIRCLSAllocate.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ FIRCLSAllocatorRef FIRCLSAllocatorCreate(size_t writableSpace, size_t readableSp
4343
readableSpace += sizeof(FIRCLSAllocator); // add the space for our allocator itself
4444

4545
// we can only protect at the page level, so we need all of our regions to be
46-
// exact multples of pages. But, we don't need anything in the special-case of zero.
46+
// exact multiples of pages. But, we don't need anything in the special-case of zero.
4747

4848
writableRegion.size = 0;
4949
if (writableSpace > 0) {
@@ -55,7 +55,7 @@ FIRCLSAllocatorRef FIRCLSAllocatorCreate(size_t writableSpace, size_t readableSp
5555
readableRegion.size = ((readableSpace / pageSize) + 1) * pageSize;
5656
}
5757

58-
// Make one big, continous allocation, adding additional pages for our guards. Note
58+
// Make one big, continuous allocation, adding additional pages for our guards. Note
5959
// that we cannot use malloc (or valloc) in this case, because we need to assert full
6060
// ownership over these allocations. mmap is a much better choice. We also mark these
6161
// pages as MAP_NOCACHE.

FirebaseMessaging/Sources/FIRMessagingPubSub.m

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -310,7 +310,7 @@ + (NSRegularExpression *)topicRegex {
310310
}
311311

312312
/**
313-
* Gets the class describing occurences of topic names and sender IDs in the sender.
313+
* Gets the class describing occurrences of topic names and sender IDs in the sender.
314314
*
315315
* @param topic The topic expression used to generate a pubsub topic
316316
*

docs/AddNewPod.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ explicit import by other Firebase pods)
5252

5353
See [Headers and Imports](HeadersImports.md) for details on managing headers and imports.
5454

55-
## Continous Integration
55+
## Continuous Integration
5656

5757
Set up a GitHub Action workflow for the pod. A good example template is
5858
[storage.yml](.github/workflows/storage.yml).

docs/AddNewProduct.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ non-Google open source project should be nested under a `third_party` directory.
6666
* `FirebaseFoo/Tests/Sample` - Optional
6767
* `FirebaseFoo/Tests/{Other}` - Optional
6868

69-
## Continous Integration
69+
## Continuous Integration
7070

7171
Set up a GitHub Action workflow for the pod. A good example template is
7272
[storage.yml](.github/workflows/storage.yml).

0 commit comments

Comments
 (0)