few more corrections

Author: Simek

docs/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/architecture/bundled-hermes.md

@@ -119,9 +119,9 @@ To implement this on Android, we've added a new build inside the `/ReactAndroid/
 You can now trigger a build of Hermes engine by invoking:
 
 ```bash
-// Build a debug version of Hermes
+# Build a debug version of Hermes
 ./gradlew :ReactAndroid:hermes-engine:assembleDebug
-// Build a release version of Hermes
+# Build a release version of Hermes
 ./gradlew :ReactAndroid:hermes-engine:assembleRelease
 ```
 
@@ -133,7 +133,7 @@ On the Gradle consumer side, we also shipped a small improvement on the consumer
 
 However, this made this line necessary in the template:
 
-```
+```groovy
 exclude group:'com.facebook.fbjni'
 ```
 

website/versioned_docs/version-0.77/timers.md

@@ -29,7 +29,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -45,7 +45,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 InteractionManager also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.78/timers.md

@@ -29,7 +29,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -45,7 +45,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 InteractionManager also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.79/timers.md

@@ -29,7 +29,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -45,7 +45,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 InteractionManager also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.80/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.81/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.82/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.83/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion:

website/versioned_docs/version-0.84/timers.md

@@ -33,7 +33,7 @@ One reason why well-built native apps feel so smooth is by avoiding expensive op
 
 Applications can schedule tasks to run after interactions with the following:
 
-```tsx
+```ts
 InteractionManager.runAfterInteractions(() => {
   // ...long-running synchronous task...
 });
@@ -49,7 +49,7 @@ The touch handling system considers one or more active touches to be an 'interac
 
 `InteractionManager` also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
 
-```tsx
+```ts
 const handle = InteractionManager.createInteractionHandle();
 // run animation... (`runAfterInteractions` tasks are queued)
 // later, on animation completion: