Use 's' instead of 'i' for signed integers

01-messaging.md

@@ -221,13 +221,13 @@ receiver to parse individual elements from `value`.
 Various fundamental types are referred to in the message specifications:
 
 * `byte`: an 8-bit byte
-* `i8`: an 8-bit signed integer
+* `s8`: an 8-bit signed integer
 * `u16`: a 2 byte unsigned integer
-* `i16`: a 2 byte signed integer
+* `s16`: a 2 byte signed integer
 * `u32`: a 4 byte unsigned integer
-* `i32`: a 4 byte signed integer
+* `s32`: a 4 byte signed integer
 * `u64`: an 8 byte unsigned integer
-* `i64`: an 8 byte signed integer
+* `s64`: an 8 byte signed integer
 
 Signed integers use standard big-endian two's complement representation
 (see test vectors [below](#appendix-d-signed-integers-test-vectors)).
@@ -978,8 +978,8 @@ be able to correctly verify signatures.
 
 ## Appendix D: Signed Integers Test Vectors
 
-The following test vector show how signed integers (`i8`, `i16`, `i32`
-and `i64`) are encoded using big-endian two's complement.
+The following test vector show how signed integers (`s8`, `s16`, `s32`
+and `s64`) are encoded using big-endian two's complement.
 
 ```json
 [

02-peer-protocol.md

@@ -446,7 +446,7 @@ completed.
 2. types:
     1. type: 0 (`funding_output_contribution`)
     2. data:
-        * [`i64`:`satoshis`]
+        * [`s64`:`satoshis`]
 
 #### Requirements
 
@@ -492,7 +492,7 @@ not contributing to the funding output.
 2. types:
     1. type: 0 (`funding_output_contribution`)
     2. data:
-        * [`i64`:`satoshis`]
+        * [`s64`:`satoshis`]
 
 #### Requirements